Hi, i have database in sql server called search, but today, i found it is changed to search (Single user), I don't know who did it. How can I change to mutilple users, also how to change the name back to search. Thanks.Use Enterprise Mangler to change the database properties from single user to unrestricted (right click on the database, properties, options, clear the restricted checkbox).
-PatP|||The set up Profiler to track this kind of change and fire someone the next time it happens.|||While firing them is rather gratifying, it really isn't a solution to the underlying problem. You really need something a bit more subtle, and lethal.
-PatP|||Oh, the way I would fire them would cover that also. :)|||Oh, I see! I'd never thought of it quite that way. Very nice!
-PatP|||Hi, you are all expert, i really don't know how to track this kind of change and fire someone? Can you give me more detail. Thanks in advance.|||We (or at least I) were making jokes about firing someone.
As far as how to track this kind of change, I'd use SQL Profiler (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_mon_perf_86ib.asp) to "watch" all of the commands being submitted to the SQL Server. The commands that you need to watch are sp_dboption (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_da-di_8c32.asp), which is used to set a database to single user mode, and ALTER DATABASE (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_aa-az_4e5h.asp) which can do it too.
-PatP|||and some help on firing someone...
http://www.integctr.com/News/EarlierNews7215.asp
http://techrepublic.com.com/5100-6314_11-5172071.html
http://www.bnet.com/abstract.aspx?&scid=1554&docid=49822
and finally...
http://www.nrahq.org/education/guide.asp|||You can probably start by making a list (and checking it twice) of all people who can do such a thing. This includes all sysadmins, members of the db_owner role in the database, and unless you have removed the BUILTIN\ADMINISTRATORS login, anyone in the local NT administrators group on the SQL Server. If you are lucky, this is a short list. Maybe even short enough that you can visit each person and ask them (quietly, of course) if they knew anything about it.
If the list is long, then you can do one of two things. Wait for it to happen again, in order to confirm there is a real problem, or set up a machine that runs profiler all day and all night. Monitor any rpc or sql statement that includes "sp_dboption" or "alter database" in the text data. Be sure you capture the hostname and login name columns.
In rare cases, I think this can be caused by a wayward maintenance plan, but I only have old and anecdotal evidence of this. Still. It may be something worth checking on.|||Thank you all very much, i need to learn that, any question, i still will ask you
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment