` MS SQL Performance (Scott Ferret ) - Icetips Article
Icetips - Templates, Tools & Utilities for Clarion Developers

Templates, Tools and Utilities
for Clarion Developers

Icetips Article

Back to article list   Search Articles     Add Comment     Printer friendly     Direct link  

Par2: MS SQL Performance
1998-12-01 -- Scott Ferret
 
If you look at any of your logs you will see that MS SQL is taking about 12 - 13 seconds to process any of your SELECTs. > Is this overhead due to MSSQL changing the > concurrency ? No. The overhead is due to MSSQL being brain dead and doing a full table scan to process your SELECT statement. MSSQL does not use non-unique indexes when processing SELECT statements. There are four ways to get decent performance out of your system: 1: Get rid of MS SQL and upgrade to a decent SQL system like SQL Anywhere or any other SQL 2: Upgrade to MSSQL 7 3: rebuild your indexes so they are unique 4: Do everything using PROP:SQL to send a SELECT with the (index=) hint


Today is November 21, 2024, 3:49 am
This article has been viewed 35304 times.



Back to article list   Search Articles   Add Comment   Printer friendly

Login

User Name:

Password: