By tag: CompatiblityLevel
0
kicks
SQL Server 2005: An error or intended behavior with Database Compatibi
It turns out you can still run CLR functions, sprocs etc when changing the compatibility level from 90 to 80.
Bug or feature?