Re: Trusted SQL Server connection (SQL 2005)
- From: Ekrem Önsoy <ekrem@xxxxxxxxxxxx>
- Date: Sun, 16 Sep 2007 21:31:26 +0300
To be able to login to SQL Server using a Windows account, then a login must be created in SQL Server Security\Login for that account or for a Windows group which consists that Windows account.
I think you better create Windows groups for your users. Create login for the Windows group who you want them to be able to login to your SQL Server and assign them necessary permissions for your database objects or whatever. It's usually a better way to create logins for groups rather than individual users. It's easier to manage groups.
You may want to have a look at the following site to learn more about creating logins in SQL Server 2005:
http://msdn2.microsoft.com/en-us/library/ms189751.aspx
--
Ekrem Önsoy
"idoek" <idoek@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:EC723436-1815-4041-812A-769D280F6507@xxxxxxxxxxxxxxxx
Thank you for your answer!
At first I thought your answer is correct, but then I logged into a Windows
machine where I know the administrator cannot access the local SQL Server
2005 using Windows Authentication.
(When I try to login to the SQL Server 2005 I get the following error:
"Login failed for user ''. The user is not associated with a trusted SQL
Server connection. (.Net SqlClient Data Provider)")
When I login using 'sa' I see that the group BUILTIN\Administrators is
defined in the SQL Server and assign to a sysadmin role, but still I cannot
login to the SQL Server using the machine administrator and Windows
Authentication.
How come? And how can I replicate this situation on another machine?
Thanks.
.
- References:
- Re: Trusted SQL Server connection (SQL 2005)
- From: Erland Sommarskog
- Re: Trusted SQL Server connection (SQL 2005)
- Prev by Date: Re: hi
- Next by Date: Re: SQL 2005, sysobjects and security
- Previous by thread: Re: Trusted SQL Server connection (SQL 2005)
- Next by thread: Re: Trusted SQL Server connection (SQL 2005)
- Index(es):
Relevant Pages
|
|