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 |
|
SimonMcGurk
Starting Member
8 Posts |
 Posted - 2007-04-19 : 09:18:40
|
| HiSorry if this seems a silly question, but my company is due an Audit soon, and this question has come up before. Basically, our development team will work on a job on a test environment, and when complete will be given access to the live server to make any changes to the database. What the auditor wants to know is what we do to ensure that the developer does not change any critical data (we store information for an insurance company), such as premiums etc.. he mentioned that he would be happy enough if we had logs which showed where data in a field had been changed.. is there anywhere within SQL Server Management Studio that would provide this information? It is not viable to block users access to the data - new fields have to updated etc in certain cases.Hope that this makes sense - any help extremely gratefully received!ThanksSimon |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-04-19 : 09:55:17
|
| Don't think so, you need third party tools like Lumigent's Log Explorer. |
 |
|
|
SimonMcGurk
Starting Member
8 Posts |
Posted - 2007-04-19 : 10:54:38
|
| Thanks - will check this out and pass onto the manager.. could be worth investing.I appreciate the reply!Simon |
|
|
|
mdkottman
Starting Member
7 Posts |
Posted - 2007-04-20 : 07:47:50
|
| A roundabout way that might solve your problem is that at the last place I was at when we had complex releases was to script out everything and have a designated release manager who only ran the script. That way the developer had no control over the release of the changes. |
|
|
|
SimonMcGurk
Starting Member
8 Posts |
Posted - 2007-04-20 : 11:18:51
|
| Interestingly, that was one of the suggestions made by the auditor today..they are obviously happiest when the least number of people can acess the live data.Thanks for the input!Simon |
|
|
|
|
|
|
Data Changes