SQL Server 2008 R2 slow processing
I have a Windows Ent 2008 32-bit installation with SQL Server 2008 R2 std edition running. The problem is that runing jobs on this installation is slower on faster hardware than on an older server with windows 2003 and SQL 2005. I have more memory allocated and they are faster processes, yet the new setup is about half as slow with the same data and same job.
I had a mirror enabled which I disabled to test, reduced log files by changing recovery model from Full to Simple and shrank the files, I have tried enabling boosting SQL priority for processing in the SQL server properties. I have also run the performance tool included with SQL, there were no advised improvements suggested for the database or server.
Are there any suggestions I can do further to improve the performance?
I had a mirror enabled which I disabled to test, reduced log files by changing recovery model from Full to Simple and shrank the files, I have tried enabling boosting SQL priority for processing in the SQL server properties. I have also run the performance tool included with SQL, there were no advised improvements suggested for the database or server.
Are there any suggestions I can do further to improve the performance?
What are the hardware configurations of both the servers? Additionally, what is the sql server memory usage on the new server?
Disk type, RAID configuration, and memory size could be factors also. Try to get the specs from the old server and the new one to compare.
ASKER
I will get the HDD drive info shortly and pot it, the new server has 2 x 500GB SATA drives mirrored. There is 8GB memory in the new server, SQL is using about 3.5GB of memory. There is no high processing, network or relative disk processing during normal use, I suppose I should monitor this during the Job that is specifically slow. New server is just idling.
Does the new server mirror those SATA drives using software RAID? If so, that'll slow things down significantly.
I'd be interested to know if the old server was using a RAID controller, and if the new server is using Software RAID.
I'd be interested to know if the old server was using a RAID controller, and if the new server is using Software RAID.
ASKER
The old server has SATA drives as well. Both new and old servers are using hardware RAID. I just found out, because I do not have access to the old server, that the old server is running Windows 2003 64-bit edition, new server is on Windows 2008 32-bit edition. I can only see this difference. I will try test the performance on a Windows 2008 R2 64-bit edition with SQL 2008 R2 64-bit edition.
Note: the database is from an older SQL2005 installation and copied, will this make a difference? I see that the database is running in SQL 2005 compatibility mode, should I change it?
Note: the database is from an older SQL2005 installation and copied, will this make a difference? I see that the database is running in SQL 2005 compatibility mode, should I change it?
Compatibility mode will not make a difference in this case. Compatibility mode is just so that newer versions of SQL Server can properly handle databases created in older versions of SQL Server. Basically....
64-bit will make a considerable difference in performance. I've seen this first hand, 32-bit vs 64-bit is night and day. We run all of our SQL Servers on 64-bit and I recommend that if possible, you do the same.
Best of luck.
64-bit will make a considerable difference in performance. I've seen this first hand, 32-bit vs 64-bit is night and day. We run all of our SQL Servers on 64-bit and I recommend that if possible, you do the same.
Best of luck.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Resolution foun not be SQL performance, but programming errors.
Do you know notice high CPU usage ?
Is the tempdb set to Autogrow.
Add another data file for the tempdb if you have multiple processers.
Have a look at activity monitor or sys.sysprocesses to see if there are any blocking transactions.
Put on SQL Profiler as well to see if it's any particular queries which are taking time.