Connect to database takes long for non-admins

Hi,

any idea why it might take longer to connect to a SQL Server for a non-administrative user than for a dbo? Same machine, just different logins...

Thanks,

Hi Thomas :-)

first thing for me would to be to have a look in the event logs, Maybe with full security logging (C2 audit) eventually also enabled you might see some more issues. But I assume that the none dbo logins will be redirected to another database than the one the "normal" users are redirected to. That might cause a delay if the other databases are closed for inactivity and have to be reopened first.

HTH, Jens SUessmeyer.

http:/www.sqlserver2005.de|||

Hi Jens,

well, we'll try full logging later... It has nothing to do with the database being closed for inactivity since if you logon twice it will take the same time...

Thanks,

Thomas

|||

Interesting... I'm trying to troubleshoot what may be a similar issue. Here are some specifics...

+ just set up a brand new 64bit server (Windows 2003 R2 64 bit O/S and SQL 2005 64 bit, Std Edition); SQL is the only thing running on this server.

+ installed this new server in the same AD domain as an existing SQL 2000 db

+ on my workstation using SQL Mgmt Studio, I am unable to connect to the new SQL2005 box (and I'm a member of the domain Administrators group), I get a "Timeout expired" dialog box. However, I *am* able to connect to our SQL 2k box.

+ again, on my workstation, I use RDP (remote desktop) to connect to both boxes just fine. So once I'm RDP'd into the SQL2005 box, I fire up SQL Mgmt Studio there... it takes well over a couple of minutes before it even finishes rendering the first screen to connect to any instances. Once it finally does come up, I can connect to the (local) db using Windows Auth.

I am completely baffled as to why it SQL Mgmt studio would take so long to open up... Any information on what it's trying to do might be helpful... It's almost like it's trying to authenticate or connect to something and timing out, although no errors are displayed and there's nothing in the event logs. It's odd to me though, as at that point (just opening up the application), it doesn't seem like it should be attempting anything like that.

-- Margo Noreen

|||

Interesting... I'm trying to troubleshoot what may be a similar issue. Here are some specifics...

+ just set up a brand new 64bit server (Windows 2003 R2 64 bit O/S and SQL 2005 64 bit, Std Edition); SQL is the only thing running on this server.

+ installed this new server in the same AD domain as an existing SQL 2000 db

+ on my workstation using SQL Mgmt Studio, I am unable to connect to the new SQL2005 box (and I'm a member of the domain Administrators group), I get a "Timeout expired" dialog box. However, I *am* able to connect to our SQL 2k box.

+ again, on my workstation, I use RDP (remote desktop) to connect to both boxes just fine. So once I'm RDP'd into the SQL2005 box, I fire up SQL Mgmt Studio there... it takes well over a couple of minutes before it even finishes rendering the first screen to connect to any instances. Once it finally does come up, I can connect to the (local) db using Windows Auth.

I am completely baffled as to why it SQL Mgmt studio would take so long to open up... Any information on what it's trying to do might be helpful... It's almost like it's trying to authenticate or connect to something and timing out, although no errors are displayed and there's nothing in the event logs. It's odd to me though, as at that point (just opening up the application), it doesn't seem like it should be attempting anything like that.

-- Margo Noreen