December 10, 2007 at 9:26 am
Does anyone have any real world experiences with database compatibility levels and performance? We have a vendor supplied app, and they have certified it to run on SQL2005, but only at level 80. We'd like to get them to level 90, but need to know if there are some legitimate reasons to do so - specifically with regards to performance.
BTW - we use transactional replication, too.
Thanks in advance.
December 10, 2007 at 9:47 am
compatibility level does *NOT* introduces performance gain/losses basically compatibility "issues" or lack of them 😀
* Noel
December 10, 2007 at 9:55 am
The compatibility level of 80, was from SQL 2000, 90 is 2005. Features introduced with SQL Server 2005 probably wont work, I assume this based on trying customised reports and trying to use pivot in a query, neither of these work unless the compatibility level is altered to 90. From this I expect none of the 2005 introduced features will work, but if the database doesn't need them you don't need to worry.
I don't know of any performance gains I expect you'd have to test that.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply