daxz (12/15/2014)
Go even one more step with DDL triggers. Log everything happening at DDL level from the servers themselves. This way you track normal releases and the dynamic changes to SQL objects by applications. Also knowing exactly what, when, where, who made the chages can be very useful.
Whilst a nice idea, I don't think that it is practical. Usually in source control we are only interested in versioning each submission otherwise we would be tracking every file changed. I, for one, would not be interested in the 10 intermediate changes to a stored procedure that occurred before the developer deemed it suitable for submission.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!