December 14, 2010 at 7:40 pm
david.jobin 9674 (12/14/2010)
From my observations .... On Windows 2008 / R2, this behaviour is expected.To make it work, you have to elevate the process with administrative privilege (UAC)
So you open SQL Mgmt Studio with run as administrator. Then you are part of BUILTIN\administrators and you can successfully log in to SQL Database engine.
Else, you have to explicitly had the user to SQL Logins.
Note that this only applies when login in locally on the SQL server. If you run SQL Mgmt Studio remotely, you don't need to explicitly grant access to user. BUILTIN\administrators will suffice.
Note, SQL Server 2008 does not add the BUILTIN\Administrators group. It does not exist as a login - so, even if you are a member that does not automatically grant you sysadmin rights to SQL Server.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
December 15, 2010 at 8:40 am
Humm...
Ohh! I know why my sql has BUILTIN\admin ... first off, I use SQL Server 2008 R2, then during setup, at the Database Engine Configuration screen, you can specify administrators for the Database Engine. I've put the builtin\administrators group. Is this setup screen also available in SQL 2008 *not* R2 ?
So in that particular case, having builtin\admin in sql logins, you have to elevate sql mgmt studio to be able to login locally on the server.
David
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply