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 |
|
CLages
Posting Yak Master
116 Posts |
Posted - 2006-06-27 : 10:50:06
|
| hi .i am evaluating RedGate software LogRescue, and i asked redgatewhy i am always getting the User Name as DBO, then they ask me.But I did not Undestand Nothing, because using my log i getthe correct user names thru the fucntion "System_user"is it possible clear this question?tks againC. LagesBy the way i am using FULLLOG now.Dear Carlos,Thanks for your enquiry. SQL Log Rescue can do what you're askinghowever there are a number of points you should be aware of.Firstly SQL Log Rescue is useless when the recovery model is set toSIMPLE because there is effectively no transaction log, and hence noinformation is recorded that SQL Log Rescue can use. Thus, if you lookin SQL Books Online you'll find that it states you can only recover datato the point of the last full backup when running with SIMPLE recovery.For SQL Log Rescue to work best you must run with FULL recovery sinceall operations are fully logged in the transaction log. This means thatyou can see exactly what happened, when it happened, and who did it (buton this last point see below). It also means that you can use SQL Serverto do point in time recovery, although to be honest it would often makemore sense to use SQL Log Rescue to undo any incorrect operations.You can also use SQL Log Rescue with databases running with theBULK_LOGGED recovery model, however under these circumstances it cannotshow full information and bulk operations will obviously not show up.Again, refer to SQL Books Online for further information.My recommendation is that you should run with the FULL recovery model,and if you want full information from SQL Log Rescue you must do this.Now, having said that SQL Log Rescue can tell you who did something,there is one proviso: if the username through which the operation wascarried out has dbo access to the database in question SQL Server willsimply record the operation as being carried out by dbo, rather than bythe username. Under these circumstances SQL Log Rescue will simplyreport the operation as having been carried out by dbo since SQL Serverhas not recorded any other information. For this reason it is extremelyimportant that you ensure that there are very few members of the dborole, and that users have only the privileges they need to use thedatabase, at which point it will become much easier to track who didwhat.Kind regards,==========================Bart ReadRed Gate Technical Support========================== |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-06-27 : 11:46:34
|
| Take it you understand the stuff about recovery model.The dbo bit just means that they are logging the database user.If you run select user_name() in the database then that will be what you get - i.e. what the user is mapped to in the database rather than the login name.If the user as an administrator on the machine or in the sysadmin role or the database owner then you will get dbo.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
|
|