sql2008 performance on a server OS very slow compared to on a standalone

Question

have a self designed application made with VS2003
it runs on a standalone XP pro laptop and zooms along   SQL2008
same code running on winserver2003, from the console machine
(same specs hardware wise as standalone, except HD and it benchmarks faster on the winserver)

to run the same job on the server OS takes 10 times longer, seriously
autocreate statistics and auto update  I turned to  False from the default of true

I have made recovery model simple and tried to find anything else that could slow it down but it just crawls and I can't find anyone else with this "problem"

Answer 1

Hello,

2 possible explanations :
- a problem coming from the fact the application has been created with VS2003 ( Framework .Net 1.1...). You should have to update the provider you are using to gain access to your database ( ODBC ). I seem to have seen a similar problem on the Forum related to Data Access

- the other possibility is related to a bad configuration of the SQL Server instance.
Could you compare the memory configured for SQL Server for your XP and your Windows Server ( and also the other configuration settings , just in case...) ?
Also, please, could you have a look on the activity of your Windows Server 2003 ? Maybe, your WS 2003 may be more loaded than your XP.

What i wrote are only common sources of problems , but you should test your application on the both configurations in the same time and have a look on the tasks managers , it is possible that you will see the origin of some problems.

Please, could you tell us the Service Pack of your XP and Windows Server 2003 ?

We are waiting for your feedback to try to help you more efficiently

Have a nice day

---

Mark Post as helpful if it provides any help.Otherwise,leave it as it is.

Answer 2

looks lke SQL2008 simply takes A LOT LONGER to open and close connections than SQL2005 did. I have a lot of open and close connections in the code and under SQL2000 and SQL2005 it ran nice and fast but SQL2008 changed that, for the worse. Going to have to change a lot of code to limit the connection opening and closing. bummer, not the upgrade I was looking for in moving to SQL2008

Answer 3

Can you post @@version? I have doubts about SQL Server 2008 connection timing being the real issue.

In addition to Papy's assistance, can anyone assist?

---

Kalman Toth, SQL Server & BI Training, SSAS, SSIS, SSRS; http://www.SQLUSA.com