I want some Moore

Blog about stuff and things and stuff. Mostly about SQL server and .Net
posts - 226, comments - 2295, trackbacks - 33

My Links



Hi! My name is 
Mladen Prajdić  I'm from Slovenia and I'm currently working as a .Net (C#) and SQL Server developer.

I also speak at local user group meetings and conferences like SQLBits and NT Conference
Welcome to my blog.
SQL Server MVP

My Books

SQL Server MVP Deep Dives 2
The Red Gate Guide to SQL Server Team based Development Free e-book

My Blog Feed via Email
Follow MladenPrajdic on Twitter

Users Online: who's online

Article Categories


Post Categories

Cool software

Other Blogs

Other stuff

SQL stuff

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?


kick it on DotNetKicks.com

Print | posted on Thursday, August 30, 2007 2:01 PM | Filed Under [ SQL Server ]

Comments have been closed on this topic.

Powered by:
Powered By Subtext Powered By ASP.NET