July 12, 2011 at 1:55 am
Change the compatibility mode to 100 and rebuild the indexes and update the stats also,did you ?
Regards,
Syed Jahanzaib Bin Hassan
BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA
My Blog
www.aureus-salah.com
July 12, 2011 at 7:04 am
Syed Jahanzaib Bin hassan (7/12/2011)
Change the compatibility mode to 100 and rebuild the indexes and update the stats also,did you ?
I haven't tried that - change compatibility to 100, indexes/runstats, then change back to 80 you mean? That might be worth a try.
July 12, 2011 at 9:11 am
Dean Cochrane (7/12/2011)
Syed Jahanzaib Bin hassan (7/12/2011)
Change the compatibility mode to 100 and rebuild the indexes and update the stats also,did you ?I haven't tried that - change compatibility to 100, indexes/runstats, then change back to 80 you mean? That might be worth a try.
If you're planning to stay on 80 mode then don't bother changing to 100 and then changing back. The point is that when you upgrade, even if you stay in the lower compat mode, the structure of the database files will have changed as part of the upgrade process. It is a good idea to rebuild your indexes after the upgrade, or at the very least update all your statistics with FULLSCAN, to make sure they are healthy in the new system and any plans.
If you're still having trouble after updating your indexes/stats please post the actual execution plans from the queries (before and after from both systems if possible).
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply