Proper way to set up SQL users
- From: Olegus <oleg.gusyev@xxxxxxxxx>
- Date: Thu, 19 Jul 2007 10:57:35 -0700
Hi,
I have an application(C#) that connects to SQL Server 2005 which is
ran on remote PC (LAN). It needs two different connection - from main
app (running under user account) and from windows service(which is
currently running under system account).
Currently SQL server has Windows authentication only.To allow both
kinds of connection I added a domain user that runs app to the
SQLServer2005MSSQLUser$XXXX$MSSQLSERVER group on the server PC and I
added special user to the SQL server logins for a windows service
connection - DOMAIN\USER$. Unfortunately I cannot add DOMAIN\USER$ to
windows users group.
The same goal can be achieved if I install windows service under User
Account - in this case it is enough to add a user to
SQLServer2005MSSQLUser$XXXX$MSSQLSERVER group. The bad thing is that
in order to switch users on app machine I would need to reinstall a
service under different account.
Another way to go is to use SQL authentication in SQL server and send
special username/pwd in connecting string.
The big problem here is that we do not want to enforce it in a case
when customer already has SQL server installed and it does not allow
SQL auth.
So, we want to have one simple way to connect to SQL server which will
work in any cases and can be setup during the app installation with a
minimum user involvement.
What is the best practices here, if any?
Thanks,
Olegus
.
- Prev by Date: Re: Cannot connect to SQL Server
- Next by Date: Re: sql 2005 connection string question
- Previous by thread: Cannot connect to SQL Server
- Next by thread: Our high end SQL server cluster is maxed out, how else to expand? Will it help to move tables off of the cluster onto other clusters or will that just create processing bottleneck on the cluster running SQL server?
- Index(es):
Relevant Pages
|
Loading
