December 11, 2008 at 10:29 am
Hello, lately we added a server, running on 8 GB RAM, 2 Quattro Core Xeon Processors, Windows 2003 64 Bit Standard SP2 and SQL Server 2005 64 Bit. I am still testing the Server but I notice some serious performance problems. I created a backup of the production database from a Windows 2000 32 Bit Server, 6 GB, with SQL Server 2005. First tests with simple selects statements indicated major performance advantages. Then I run some a stored procedures we are using to create a table for a data warehouse. On the old 32 Bit server it takes 1.5 hour, on the new server the same SP takes 2.5 hour. I am running a maintenance plan to update the statistics (FullScan) rebuild all the indexes and run the SP’s multiple times. The tuning advisor did come up with any recommendations how to improve performance. I know I still have to do more testing using the Profiler and fine tuning the execution plan. Does anyone have any other thoughts what I can do to fix the problem?
December 11, 2008 at 1:15 pm
Couple of thoughts:
Is tempdb configured properly on the new server (i.e. on its own drive, 1 tempdb file per processor is recommended - this might vary, is it sized properly etc)?
What is causing the difference in times between the 32 bit and 64 bit executions (i.e. is it taking more time for I/O related or CPU related tasks in the 64 bit environment etc)
December 11, 2008 at 3:36 pm
Have you compared the execution plans?
What version of SQL Server 2005 std, enterprise? There are differences in memory use in the 2. Is SQL Server using the memory it should? Is storage the same on both servers?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
December 12, 2008 at 10:09 am
Thanks for your response. Right now the tempdb resides on the same drive than all the other db files. The OS is on the C:\ Drive and the SQL server on the D:\ drive. I have to find out if I can change that.
December 12, 2008 at 1:54 pm
Jack Corbett (12/11/2008)
Have you compared the execution plans?What version of SQL Server 2005 std, enterprise? There are differences in memory use in the 2. Is SQL Server using the memory it should? Is storage the same on both servers?
Hi Jack,
The execution plans look the same. We are using Version: 9.00.3073.00 for the SQL Sever 2005 64 Bit box. I am still running tests checking the profiler results for the memory usage
Thanks
Andreas
September 13, 2009 at 8:40 am
Hello ,
Were you able to solve this problem? I have the same problem. DId everything nothing works. Please let me know.thanks
September 14, 2009 at 8:17 am
Hi,
we have not been able to figure out what is causing the problem. We decided to use the 64 bit system for different databases and kept the database with the 'slow' stored procedures on the 32 bit system. We might revisit the problem at a later point as we are working on a major overhaul of the database design.
September 15, 2009 at 9:54 am
thanks..will update you if i find a solution for it
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply