March 19, 2008 at 8:50 am
We have encountered a situation where one of our developers has made changes to a schema (change of datatype) which has had a major knock on effect re our applications. Is there anyway by which I can identify the culprit and the time that this occurred - ie is there a way of tracking schema changes? btw we are using SQL Server 2000.
March 19, 2008 at 9:21 am
Richard Edwards (3/19/2008)
We have encountered a situation where one of our developers has made changes to a schema (change of datatype) which has had a major knock on effect re our applications. Is there anyway by which I can identify the culprit and the time that this occurred - ie is there a way of tracking schema changes? btw we are using SQL Server 2000.
Richard,
You could use a third-party log viewer to look at the log file (or log backups) to see who changed what. This though requires that you maintain log backups.
I was going to suggest using ddl triggers but then I noticed you're using SQL 2000, not 2005. Another alternative is to enable C2 auditing on the SQL Server - this basically logs everything that happens on your SQL Server. I'm not sure about the overhead of this so it's something you'd have to investigate.
Failing all of that, you'd have to look at a source control solution for SQL Server but any source control solution is only as good as the people that use them - in other words, there's nothing to stop a developer going onto the SQL Server and bypassing the source control methods you put in place.
Of course, you could deny developers from making schema changes altogether ;).
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply