Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got an interesting sounding problem with SQL queries run from a particular machine. This machine is a VM running Windows Server 2003, and it has SQL Server Express 2005 on it.

The VM was migrated from a VMWare Player image into a proper VMWare Workstation setup. It ran fine when it was running under the Player only (on different physical hardware.)

From this machine, if I run osql and connect to its own SQLEXPRESS instance, queries run horribly slowly (10 minutes to return and print 1000 rows from a select statement.) If I run osql and connect to another database server, queries run at a similar speed.

From this machine, if I use SSMS to run a query it performs fine! The same table is open for editing in less than a second. I ran osql on another machine, and connected to the VM with this issue. Querying the exact same test as before runs very quickly, too.

The main reason this is an issue is because our webapps on this VM run as slowly as osql does, instead of the more normal speed exhibited by SSMS. These webapps use v2.0.50727 of the standard System.Data dll for their queries and connections.

Has anyone seen these symptoms before, and/or knows how to fix it?

share|improve this question
up vote 1 down vote accepted

This actually appeared to have been an issue with having Tracing turned on in the ODBC data sources control panel.

To check this setting:

Start -> Settings -> Control Panel -> Administrative Tools -> Data Sources (ODBC) Select the Tracing tab. Make sure Tracing is turned off.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.