Well, you could break the list up into smaller chunks and send each list to
the SP as a parameter (using CFSTOREDPROC). In the SP, default each
parameter to NULL, then dynamically build your SQL statement, and only
include those parameters which are not null.
Bob
-----Original Message-----
From: Philip Arnold - ASP [mailto:[EMAIL PROTECTED]]
Sent: May 8, 2001 12:47 PM
To: CF-Talk
Subject: RE: Limit on SQL passed via CFQuery to SQL Server?
> If I were you I'd put it in an SP. I know there used to be a limit to the
> length of an SP in 6.5 but as far as I'm aware this issue was
> addressed in 7
My problem is that the majority of the data is the list of Identities used
in the IN()
I'm not sure how if a SP can handle this better than a CFQuery
Philip Arnold
Director
Certified ColdFusion Developer
ASP Multimedia Limited
T: +44 (0)20 8680 1133
"Websites for the real world"
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
