Re: Cause SQL Server Restricted Mode (db_owner, dbcreator,)
From: Michael Hotek (mhotek_at_nomail.com)
Date: 04/12/04
- Next message: Michael Hotek: "Re: Rename SQL Default instance in cluster"
- Previous message: Rob Oldfield: "Re: So exactly what IS clustering?"
- In reply to: Dan: "Cause SQL Server Restricted Mode (db_owner, dbcreator,)"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 12 Apr 2004 03:20:50 -0400
The only thing that can do that is an administrator. If it is a new
database, it will look exactly like that since SQL Server uses the principle
of having to explicitly grant access. But, if it is an existing database,
an administrator had to have changed the security. You are saying that no
one did this. I'd more accurately say that no one is willing to admit to
having done that. How can you find out? Download Log Explorer from
Lumigent Technologies and point it at your tran log + tran log backups. It
will show you pretty explicitly when the security was changed and by whom.
I'd also recommend taking a look at their companion product Entegra which
can notify you immediately when security changes and a whole host of other
things change.
-- Mike Principal Mentor Solid Quality Learning "More than just Training" SQL Server MVP http://www.solidqualitylearning.com http://www.mssqlserver.com
- Next message: Michael Hotek: "Re: Rename SQL Default instance in cluster"
- Previous message: Rob Oldfield: "Re: So exactly what IS clustering?"
- In reply to: Dan: "Cause SQL Server Restricted Mode (db_owner, dbcreator,)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
