Brigadur (2/1/2012)
L' Eomot Inversé (2/1/2012)
That's a good idea! With the warning option, i was thinking of all existing code out there (not mine of course 😉 ) that relies on defaults.
+1.
Error messages could break existing code but there could be a session SET option that could possibly show warnings to most common coding mistakes perhaps. Like some recommended guidelines. But with advices from people here, not only the SQL Server team (who love procedural coding sometimes).
And profiler has two events for catching deprecated code. Maybe a few more events there? 🙂
Best regards,
Andre Guerreiro Neto
Database Analyst
http://www.softplan.com.br
MCITPx1/MCTSx2/MCSE/MCSA