SQL Server 2005: An error or intended behavior with Database Compatibility?
An interesting topic came up a few days ago in the forums about database compatibility.
It turns out you can still run CLR functions, sprocs etc when changing the compatibility level from 90 to 80.
Of course i had to test this behaviour because i had a hard time believing it.
i used my high precision timer for performace measurements which is written in C# as a test bed.
You can find the whole script in that post.
When i created the database and all CLR functions I changed the compatiblity level to 80 with:
EXEC sp_dbcmptlevel testCLR, 80;
Then I tried using the CLR functions and they worked just fine. I didn't expect this.
If i dropped a function i could NOT recreate it again which was expected.
Is this a bug or intended behaviour? And why?
