Well, MS SQL Server performance tuning is a pretty big topic. It wouldn't be fair to make a general statement that 65 million records is "more than MSSQL can handle", but it may be more than their current configuration can handle. This depends on many factors including their hardware (CPU, RAM, etc.), what else is running on the machine, how much data is being requested, etc.
The design of the database will also have a major impact. Looking at which indexes exist, and whether any of them are being used (this can be done in QA by looking at the Estimated Execution Plan (press ctrl-L)). Even if no indexes are being used, MSSQL can generally handle a table scan of a large table, but don't expect it to be fast. It would be a good idea to find out what "crapping-out" means. MSSQL usually gives you some indication of what's wrong. It is a time-out? Are they running out of disk space (a definite possibility if they're trying to sort the result set)? Any other error messages? Bob ----- Original Message ----- From: "A. Karl Zarudny" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 12, 2002 4:30 PM Subject: [CFTALKTor] searching 65 million records with MSSQL > Hi everybody. > > Hopefully one of you can provide some insight to this one. I recently met > someone who said they were having trouble with MSSQL crapping-out (that's [message truncated] - You are subscribed to the CFUGToronto CFTALK ListSRV. This message has been posted by: "Bob Silverberg" <[EMAIL PROTECTED]> To Unsubscribe, Please Visit and Login to http://www.CFUGToronto.org/ Manager: Kevin Towes ([EMAIL PROTECTED]) http://www.CFUGToronto.org/ This System has been donated by Infopreneur, Inc. (http://www.infopreneur.net)
