April 8, 2016 at 4:24 am
Dear All,
Last night we migrated from 2005 to 2008 r2 , this box has higher config than the old one (256 gb ram, 4 cpu's etc..)
There were few report screens which used go get timeouts last year which we had fixed them. Now after migration yesterday, we are getting exactly same timeouts on those screens again. The error is same SPC timed out and I am sure the SPC is the latest one on new DB.
I even tried update statistics after restoring the DB from 2005 to 2008 r2, but still the same issue.
My Questions:
When DB is restored on 2008 r2, should there be any DB level activities performed like re-indexing etc ,?
I am asking this seems to be purely a DB related issue. DB is on clustered environment and the configs are high compared to old DB.
Any inputs would be useful.
April 8, 2016 at 11:32 am
There many potential causes for the observed behavior, and I could only wildly speculate based on the information given (just one example would be queries that use parallelism regressing when more cores are available; I've seen that many times).
Ultimately, the approach to take will be the same as for diagnosing any other change in performance.
You'll want to look at execution statistics and query plans for the now-problematic code, and use that information to determine the problem.
If you still have the old server running, you can take it a step further and do the same exercise on that server, comparing results.
If you need some help examining the query plans and execution statistics, just post what information you can here. We like execution statistics, actual execution plans, and (if possible) some sample data (in the form of DDL for the involved objects and INSERTs for the sample data) that reproduces the poor performance.
Cheers!
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply