procedure and then you could call that via CFEXECUTE and tell CF not to
wait for it to finish. Then CF will call the script which will call the
stored procedure and then it will move on and do its job.
John
-----Original Message-----
From: DURETTE, STEVEN J (AIT) [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 05, 2004 6:19 PM
To: CF-Talk
Subject: RE: cfmx - request timeout setting
Tony,
The only thing I can say to that is run it one way , then run it the
other way and see which is faster.
There is an article about Query performance here:
http://www.databasejournal.com/features/mssql/article.php/3298411
<http://www.databasejournal.com/features/mssql/article.php/3298411>
Steve
-----Original Message-----
From: Tony Weeg [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 05, 2004 5:38 PM
To: CF-Talk
Subject: Re: cfmx - request timeout setting
so...
does that looping effect buy me anything, or should i just run the
whole shebang and not worry about rowcount?
i guess my question is...does this help in the deletion process? help
= increased speed/less downtime?
thanks!
--
tony
Tony Weeg
human.
email: tonyweeg [at] gmail [dot] com
blog: http://www.revolutionwebdesign.com/blog/
Check out http://www.antiwrap.com to send websites to your friends.
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
