Results 1 to 1 of 1
2007-11-27, 06:23 #1
- Join Date
- Jan 2002
- Brookings, South Dakota, USA
- Thanked 0 Times in 0 Posts
Work around connection string needed (A2k3/A2k7)
I'm trying to sequentially connect to multiple sql servers, both 2000 and 2005, from Access 2003 or 2007. Due to sensitivity of data, in compliance with "our" imposed version of the Sarbanes-Oxley Act, the group username of BuiltinAdministrators has been removed (disabled actually) from the list of sysadmins in about 1/4 of our SQLServers. I (we as sql db admins) have 2 username accounts. One for our desktop/day to day usage and an admin username for db server administration tasks.
We can only access these "locked down" servers by logging into SSMS as SA or we do have a network account which is used as an SQL services owner that can also be used.
It is this network account I want to use.
As far as I can tell, there are 2 ways to connect to SQLServer through code using ADO and Access: a trusted connection using the current logged-in Windows user ("Integrated Security=SSPI" or "Trusted_Connection=True") or using standard security (SQL Authentication). <edit>It is logistically impossible to use standard security as each server's SA password is different and I don't have or want a db table with ALL the passwords. I am also using this program to ferret out clandestine installs of SQLServer, which means I wouldn't be able to access that server anyway with standard security.</edit> So this would require me to set up some type of impersonation to be able to log into a SQLServer. I have not been able to find a way to be able to do that.
Is there a way to use impersonation in Access? and if so, which type library do I need to reference?
Is there a method to be able to use SQLServer?
<long shot>Can I use .NET? again if so, which type library is referenced?</long shot>
Thank you.<IMG SRC=http://www.wopr.com/w3tuserpics/gdrezek_sig.jpg>
"Those who dance are considered insane by those who can't hear the music" - George Carlin