December 8, 2010 at 10:52 am
For months, I've been wrestling with the db security police at my current client because I only have limited visibility. For example, they use four or five different schemas but I can only see the dbo schema on the QA and Production SQL Server 2005 instances. (I'm using the SQL Server 2008 client, i.e. SSMS.) They claim to have placed me in the right security groups in active directory but I still can't see anything.
Finally, in exasperation and on a hunch, I fired up the SQL Server 2005 client and, lo and behold, I can see everything I'm supposed to be able to see.
I can't think of any reason why the client should make any difference from a security standpoint. After all, isn't it supposed to be backwards compatible?
The only thing I can think of, and I think it's a long shot, is that I was not a local admin on the box when I installed SQL Server 2008. (The box came pre-configured with SQL Server 2005.) I'm trying to get that changed but they're really adamant about users not installing software on their own machines, particularly us consultant types. The only reason I installed SQL Server 2008 myself was because the help desk guy didn't have a clue and the fact that it installed successfully would seem to rule that out as an issue.
Does anyone have any thoughts on this matter?
"Beliefs" get in the way of learning.
December 8, 2010 at 11:16 am
Try running SSMS as an admin. Right-click and select "Run as administrator". See if that helps.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
December 8, 2010 at 12:30 pm
Unfortunately, it's prompting me for a password and I don't know the password for the administrator account. (I'm running XP) I'm not sure that would help me much anyway. The whole point is to access the remote instance with my username.
Thanks anyway.
"Beliefs" get in the way of learning.
December 9, 2010 at 7:53 am
For anyone paying attention the issue is resolved. I uninstalled SQL Server 2008, made myself an admin on the box and re-installed SQL Server 2008. Suddenly everything was visible to me on other servers that I couldn't see before.
I can't imagine why the installation user on the client box was relevant, from a security point of view, when connecting to remote servers. If anyone has any theories I'd be interested to hear them. Obviously, it occurred to me that it might be a problem and that's why I did what I did but I can't really say why I thought it might be a problem. It was just instinctive.
"Beliefs" get in the way of learning.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply