June 6, 2012 at 3:03 am
I have a database of 50 GB running on quad-core dual processor with 32 GB RAM. The application is running very slow here.
I backed up the database and restore it another staging server with dual core processor and 8 GB RAM. The application working very fine here.
What could be the reason for that?
I am new with Sql Server 2005, so any help will be appreciated.
June 6, 2012 at 7:52 am
irumman (6/6/2012)
I have a database of 50 GB running on quad-core dual processor with 32 GB RAM. The application is running very slow here.I backed up the database and restore it another staging server with dual core processor and 8 GB RAM. The application working very fine here.
What could be the reason for that?
I am new with Sql Server 2005, so any help will be appreciated.
It COULD be any number of things. Unfortunately there is nowhere near enough information to even think offering and idea of what is the cause. What do you mean by "The application is running very slow here."?
Do you have some sort of application that is running slow and you think sql is the reason? Have you updated statistics? Indexes? Is there a slow network connection to this box? Is DNS resolution really slow to this box?
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply