March 22, 2009 at 8:47 pm
Some changed from MULTI_USER to single, is there way to find out how it happend and when and who did?Thank you
March 22, 2009 at 10:37 pm
SQL Server logs will have this info...
March 23, 2009 at 6:24 am
I don't see it, is there particular job or command?
March 23, 2009 at 6:52 am
If you don't have an existing SQL trace, there's no way to tell who did this. The SQL log should have an entry saying that it happened, but not who did it. If you can find that entry, check the time and see if there's a job corresponding.
One possibility is that you've got the option 'Automatically fix minor errors' checked in a Database consistency check task (in a maint plan). If errors are found, the DB will be switched to single user so that the errors can be fixed.
That check box should always be unchecked.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 23, 2009 at 2:58 pm
Lacking a trace I'd start to investigate T-SQL jobs that backup or possibly reindex databases. Sometimes homegrown scripts contain these 'goodies'.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
March 24, 2009 at 9:43 am
rudy komacsar (3/23/2009)
Sometimes homegrown scripts contain these 'goodies'.
Interestingly I see this sort of thing FAR more often in the scripts that are built through wizards, maintenance plans, etc.. In my experience homegrown scripts rarely include this sort of thing since it is usually an extra option that a basic script will not include.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply