On our production system we have this NT group called as [Domain Name \Domain Users]. In our team none of us recall adding this group on our production and moreover; this group is sysadmin on production system, which scares me because, if, no one added this group on our runtime system then how did it become sysadmin on runtime system? I'm a newbie to sql 2005 security. Please help. Here is our production system configuration: 2 X Windows 2003 x64 R2 SP2 EE -- Active Passive configuration. Sql 2005 SP2 EE. Thanks,
(kulkarni.ninad@gmail.com) writes: > On our production system we have this NT group called as [Domain Name > \Domain Users]. In our team none of us recall adding this group on our > production and moreover; this group is sysadmin on production system, > which scares me because, if, no one added this group on our runtime > system then how did it become sysadmin on runtime system? I'm a newbie > to sql 2005 security. DROP LOGIN [Domain Name\Domain Users] Then staffs the phones and be prepared if someone screams. -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Maybe, it sneaked in through one of the production change scripts. Linchi "kulkarni.ninad@gmail.com" wrote: > On our production system we have this NT group called as [Domain Name > \Domain Users]. In our team none of us recall adding this group on our > production and moreover; this group is sysadmin on production system, > which scares me because, if, no one added this group on our runtime > system then how did it become sysadmin on runtime system? I'm a newbie > to sql 2005 security. > > Please help. > > Here is our production system configuration: > > 2 X Windows 2003 x64 R2 SP2 EE -- Active Passive configuration. > Sql 2005 SP2 EE. > > Thanks, > >
