Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
tdishman
Starting Member
2 Posts |
 Posted - 2006-12-19 : 08:48:57
|
| OK, here's the situation. Almost every table in my database has a column to log the suser_sname() of the domain user responsible for adding the record. For the most part this works great. However, I've noticed that atleast 1 user (maybe more users, but definitely this user) sometimes gets logged as not the DOMAIN\user, but rather as SERVER\Administrator (where SERVER is the name of the SQL Server).My app connects to the SQL 2000 Server via Windows Authentication (connection string: SERVER=servername;DATABASE=dbname;Integrated Security=SSPI;Connect Timeout=10;Pooling=false).One thing that might be important to note is that the user rarely restarts/logs off of their computer (unless needed). Nobody here logs out at night.I am by no means an expert in SQL Server permissions or security, but I definitely need a reliable way to monitor users. |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2006-12-19 : 08:56:59
|
| Group membership has precedence when you are using Integrated Security SSPI.If this certain member is part of the LOCAL ADMINISTRATOR GROUP, this is the account used instead of the personal account.Peter LarssonHelsingborg, Sweden |
 |
|
|
tdishman
Starting Member
2 Posts |
Posted - 2006-12-19 : 09:01:35
|
| That makes sense, but why would it sometimes log his suser_sname() correctly, but not other times? |
|
|
|
|
|
|
suser_sname() oddities