Comments
2 comments
-
Hi Barry
Within SQL Source Control there is no facilty to define a checkin policy. However there is new Red Gate product called SQL Test, see this LINK
You can then create your own custom tests toPrevent against the use of SELECT *
OR ensure that all tables have specific columns contained within them (RowID/ Loadeddate)
You and your colleagues can run the tests prior to committing the changes via SQL Source Control.
I hope this helps.
Many Thanks
Eddie -
Hi Barry,
SQL Source Control will now let you enforce TFS policies (if you use Microsoft's Team Foundation Server as your source control system).
You can create a custom TFS policy to enforce this behavior (see here: http://msdn.microsoft.com/en-us/library/bb668980.aspx).
Or you can use the testing policy to run SQL test for each checkin: http://stackoverflow.com/questions/4105086/enforce-tests-run-before-tfs-check-in.
More general information on TFS is here: http://msdn.microsoft.com/en-gb/vstudio/ff637362.aspx
Anna
Add comment
Please sign in to leave a comment.
Not sure if this is possible, but is there anyway to define a checkin policy inside/ alongside SSC to stop developers checking in database code that they shouldn't?
i.e. Prevent against the use of SELECT *
OR ensure that all tables have specific columns contained within them (RowID/ Loadeddate)
Barry