Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy is database access (SQL Server) slower on Windows 7?
    primarykey
    data
    text
    <p>We use SQL Server 2000 to store results from our test equipment. We have installed our test software on Windows XP machines and do not have any problems with the time it takes to query from and write to the database.</p> <p>When we recently installed a Windows 7 machine the database access appears to be taking 20 to 100 times as long. We connect to SQL Server using a COM interface passing a connection string that holds the server name, login ID and default database:</p> <pre><code>Provider=SQLOLEDB.1; Persist Security Info=False; User ID={Login name}; Initial Catalog={Database name}; Data Source={Server name} </code></pre> <p>I have tried using a .net database interface but this does not provide any significant improvement in speed.</p> <p>Is SQL Server database access from Windows 7 just much slower that Windows XP or is there any way to increase the performance of our code?</p> <p><strong>Extra detail</strong></p> <p>We have SQL Server 2000 running on Windows 2003 server. This is our production database that stores test results from over 40 test stations. We have plans to upgrade to SQL Server 2005 but this is dependant on another project that will not be complete for approx 6 months. The client PC (the one accessing the database) is Windows 7.</p> <p>I have tested using a Windows 7 client PC accessing SQL Server 2005 running on Windows 2003 server and found similar results.</p> <p>As a quick test I have run a SELECT query 100 times on both Windows 7 and Windows XP with Windows 7 taking approx 30 seconds and Windows XP less than 1 second to complete. This has been repeated with both SQL server 2000 and 2003 amd the same difference is seen.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload