We installed SQL 2017 standard edition. Taken the 2008r2 server database backup and restored into new 2017 server. Didn’t change the compatibility level. Same memory allocated as 2008r2 and did the update stats but seeing performance issues.
Start with the "Key Configuration Options" in the following article. Every single thing there can make a pretty good difference.
Change is inevitable... Change for the better is not.
Thanks Jeff. According to the link performance regression happens with LEGACY_CARDINALITY ESTIMATION, when changed the database comparability level from old version(100) to native/new version(140). Here we didn’t change the compatibility level so LEGACY_CARDINALITY ESTIMATION is off.
Have you ever investigated MS Query Tuning Assistant ?
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
Hall of Fame
You might try DBCC Updateusage.
I've had to run that coming off some old servers to fix performance issues if it seems storage is your related wait types.
Viewing 5 posts - 1 through 4 (of 4 total)