What would cause SQL Server 2000 Enterprise Edition
databases to be in access restricted mode where only
db_owner, dbcreator, and sysadmin?
SQL Server was not placed in access restricted my any
administrator.
This is an active/active cluster with SQL Server 2000
SP3A with Windows 2000 Advanced Server.
Could the cluster place SQL Server 2000 in a access
restricted mode?
If SQL Server 2000 resources were very low for extended
period would the cluster or SQL Server place SQL Server
in access restricted mode?
Please help me resolve this issue.
Thank You,
Dan
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
Thursday, February 16, 2012
Cause SQL Server Restricted Mode (db_owner, dbcreator,)
Labels:
access,
cause,
database,
db_owner,
dbcreator,
editiondatabases,
enterprise,
microsoft,
mode,
mysql,
onlydb_owner,
oracle,
restricted,
server,
sql,
sysadminsql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment