October 6, 2010 at 11:21 am
HI All,
I have migrated a database to new server (2005 to 2005).
Old server config is: 4 processors with 32bit OS, 4 GB RAM, RAID5
New server config is: 2 processors with 64 bit, OS 6 GB, RAM RAID5
SQL Server : 2005 EE on both the servers
After migration, I have updated stats, recompiled all objects on the new server.
But today i am gettimg operation timed out errors very frequently, what could be the problem.?
Thanks.
October 6, 2010 at 1:17 pm
Any blocking process?
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 6, 2010 at 1:18 pm
With only 2 procs, make sure your MAXDOP is set to 1. If SQL tries to run any kind of parallelism, it could take up both CPUs and then that would definitely cause timeouts.
October 6, 2010 at 2:10 pm
No, There is no blockings.
Thanks
October 6, 2010 at 2:16 pm
MAXDOP is query level setup. how can i put this hint on every sql..?
There are many process and SP's running on the database.
Thanks
October 6, 2010 at 2:19 pm
exec sp_configure 'Show Advanced Options',1
reconfigure with override
exec sp_configure 'Max Degree of Parallelism',1
reconfigure with override
See if that helps at all. Downgrading from 4 cpus to 2 cpus is going to have a noticeable hit on performance.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply