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 |
|
DBADave
Constraint Violating Yak Guru
366 Posts |
 Posted - 2005-08-01 : 13:07:32
|
| I noticed today one of our production database servers is incorrectly reporting, through Enterprise Manager, database names from within various job steps. Instead of the correct name being displayed we are seeing the first database that appears in sysdatabases alphabetically.The problem appears to be related to a Windows Group for our DBAs. We tested removing the group from SQL Server and adding my id directly to SQL Server. I was then able to see the correct database name for the job steps in question. When my id was removed and the DBA Group added back to SQL Server, the problem reappeared. What makes things even stranger is we recently added a service account to this group (not the SQL Server service account). When I connect as the service account id Enterprise Manager displays the correct database names. Not sure how a Windows Group can influence the way Enterprise Manager displays database names in SQL Server job steps, but there definitely is some relationship between the two.Any idea what is causing this problem and how to correct it?Thanks, Dave |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-08-01 : 15:18:48
|
| It sounds like someone has updated the system tables directly instead of through the system stored procedures. In previous versions of SQL Server, I found myself regularly doing this, but not anymore. In fact, I haven't had to this in about 4 years now.You'll need to contact MS to figure out exactly what is going on though.Tara |
 |
|
|
DBADave
Constraint Violating Yak Guru
366 Posts |
Posted - 2005-08-02 : 13:31:10
|
| Here is an update. We noticed the service account that was not experiencing any problems not only was a member of the group in question, but also had permissions granted directly to the id. When we removed the id from the server, so it would only rely on group permissions, the same problem occurred.We tried this on several other servers and found that any Windows NT Group experienced the same issue. The groups all have been provided db_datareader in all databases, except model, and have been added to TargetServersRole. We also noticed that within any job step if we select the drop down for databases, we only see databases containing the Guest account. The problem appears to be related to TargetServersRole.A consultant I am working with was able to recreate the problem on several servers at other companies. We both wonder if this is a bug related to TargetServersRole. It's not specific to Enterprise Manager since I was able to produce the same results using DBArtisan.Any suggestions?Dave |
|
|
|
|
|
|
|
|
EM displays incorrect database name in job steps