Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-05-24 : 09:44:23
|
| Ian writes "In the organisation i work for, we experienced a problem which may have been a modification to a table which caused a stored proc to fail. This problem then disappeared. I think someone changed it when they realised they had screwed it up. Is there a way of finding which user modified the table structure, or if it was changed at all." |
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2002-05-24 : 09:51:56
|
| Not an automated one.Your best option is to bring in a source control process where all objects are kept in script and in source control. To change an object you need to check a script out, make the change and check it back in.I know it sounds like a pain, but it will be best in the long run.Damian |
 |
|
|
JamesH
Posting Yak Master
149 Posts |
Posted - 2002-05-24 : 11:21:27
|
| You can also look in BOL and do a search on Create Trigger. In Section E. use COLUMNS_UPDATED there is an example of using a trigger with an auditing table for changes to a table. Section F. also provides further information for using more than 8 columns.JamesH. |
|
|
|
JamesH
Posting Yak Master
149 Posts |
Posted - 2002-05-24 : 11:26:24
|
| My mistake, I mis-read the problem.I'll try again:In the case of a table being changed, I would definately look at code review and having only the DBA implement ANY changes to data structure for production environments. Changes on production systems can be distasterous if not properly managed...As if I had to state that.JamesH. |
|
|
|
|
|
|
Tracking who changed a table.