Code analysis for Sql Project
I’m not a fanatic of Code Analysis, at least I know that it is quite impractical trying to remove all warning of fxcop analysis, but I strongly advice you to run code analysis on your code, and give it a shot from time to time. First of all is a good way to find potential bug, then you will always learn new and more standard way to write your code.
The good stuff about VSTS Db edition is that it contains code analysis even for your DB.
As an example of typical warning you get here is some example.
Someone had designed a function where a datetime is passed and the function returns a varchar, but varchar(19) seems not to be big enough to contain the date.
This one also is an important warning, since this code is into a table valued function, using a SELECT * will change the shape of the returned table, so it is really better to specify all the field you needs and no more. Warning are subdivided by area, previous 2 are from Microsoft.Design, others are devoted to performance
But there are more really interesting warning like this one.
Since a Database Project contains everything about the Db, Visual Studio is able to spot problematic areas regarding missing index. The analysis is indeed quite deep
While you surely not want to remove all of this warning, some of them are really interesting because they can spot potential problems in your database design.