Disadvantages of running 80 compatibility on 2005?

I have a hosted solution where the web host provider tells me I'm running on a 2005 platform, but when I check the DB options, it shows compatibility level 80. The provider tells me I'm not losing any performance by running in the lower compatibility mode. Is this truly the case? What else am I losing out on in terms of features or capabilities?

when you have ealier version compatibility , you will have different behaviour for same command .

eg

create table #tt (tablesample int)

run the above mentioned command in both Comp - 80 and comp-90 database and see the behaviour change

Otherewise i don't think there is any performance degradation using lower compatibility level.

Refer sp_dbcmptlevel (Transact-SQL) in BOL it has very deatiled description about it

Madhu

|||

I am aware of the difference in command behavior, I'm not too concerned about that ...

thanks for the note on performance, any chance you have any references I can check out? I'm not in a position to benchmark between 2000 and 20005 myself right now. what I was looking for, in addition to the performance issue, was whether or not I lose features like Service Broker and other 2005-specific stuff if I'm running in 80 ...

|||Yes, FEATURES MAY BE LOST, Service Broker in particular requires a 90 compat level....however I think the ultimate answer is it depends on the feature.|||The answer depends on the feature. Yes, running in 80 compatibility mode, you can pretty much expect to not be able to utilize any of the features brand new to SQL Server 2005. Just about all of them that I've come across require 90 compatibility mode. Setting the compatibility mode is really designed to allow a short term bridge between versions for things that need to be changed. It isn't intended to be running in that mode for an extended period of time.|||Thanks all for the replies.