September 20, 2008 at 4:20 am
Let's take some advantage of the new features of SQL2005 :w00t:
Post the Execution plan !
Run your query (include actual execution plan (ctrl+M)) in SSMS on both boxes and on the result pane take the
Execution plan tab. Rightclick and perform "Save As"
It generates .sqlplan files.
Attach them to your post overhere.
It doesn't reveal any data, just the query, the plan and the objects involved.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
September 20, 2008 at 4:42 am
Have you manually checked the indexes & stats in question? You can see them from the execution plan.
Any significant fragmention in production?
Also, have you run sp_autostats against the table(s) in question to see if the stats are up to date in production?
Are both servers the same spec? Processors, memory (physical and amount allocated to sql server), disk etc?
September 20, 2008 at 10:28 am
Clive Strong (9/20/2008)
Have you manually checked the indexes & stats in question? You can see them from the execution plan.Any significant fragmention in production?
Also, have you run sp_autostats against the table(s) in question to see if the stats are up to date in production?
Are both servers the same spec? Processors, memory (physical and amount allocated to sql server), disk etc?
as i mention at my first post.i did a full backup and restore on the Test server so if i have an indexes that are fragmented it will be on both server's.
the Test server is only P4 with 1GB Memory 1 partition in Mirror.
Viewing 3 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply