Extend 'Find Invalid objects' to find other 'problems'. E.g. unaliased fields, wildcards etc.
It would be lovely to find other elements in the database that may not stop it from working right now but are 'problems waiting to happen'. Other examples might be to search for field names that clash with reserved terms.
Stephen
shared this idea
-
Urban Fransson
commented
When opening a procedure there might some red dots by the scrollbar, this will result in an error when running the procedure, it would be great to find these errors as well.
-
Justin Caldicott
commented
There are lots of best practise style issues reported by SQL Cop. (http://sqlcop.lessthandot.com/) Are there any of these tests that you would particularly like to see added?
-
Simon
commented
It would be quite nice to be able to specify a database level to validate against too. For example 2008 needs semi-colons before CTEs but 2005 doesn't.
Sometimes when moving a database between servers I first ensure there are no invalid objects that will prevent SQL Compare from being able to generate the new database, currently I have to run SQL Compare, find an issue and fix it then repeat until there are no more issues. If Find Invalid Objects could detect those 'potentially invalid objects' that would be good