July 19, 2005 at 9:24 am
Hello!!
Our company recently moved to a corporate Windows 2000 Network and AD from Novell and all our servers were moved from our little domain. We are seeing a wierd problem with SQLSever since our move. The sever that has SQL Server is working fine and we are able to register the server in Enterprise Manager. However, it sits and hangs when trying to browse the Databases or Management nodes (all other nodes are ok). We can also get to Query Analyzer and queries against any of the the database tables work just fine .. UNLESS Query Analyzer tries to browse for the databases (to populate that database dropdown or display the Object browser) .. in that case, it sits and hangs.
We have installed Service Pack 4 and this did not resolve the problem. The hotfix for RAM over 2 gig on the server does not apply in our case. Has anyone experienced this problem before? We rebooted SQL Server yesterday and after a couple of reboots, it worked (the Query Analyzer issue remained), but we are now back to the same issue.
Any clues, suggestions, and of course fixes would be much appreciated!
Thank you!
Artie
July 20, 2005 at 5:09 pm
I'd suggest using profiler to capture all SP:StmtStarting and SQL:StmtStarting to see where it's hanging.
Of course, try this with an appropriate hostname filter or when there's zero/minimal other activity on the server because output will be hefty.
(it might turn out to be some AD-related call from within EM or some server-based SP... then again it might be something else entirely)
Cheers,
- Mark
July 26, 2005 at 8:27 am
Sounds strange if this started happening if you just moved your SQL Server.
It sounds like a common system table blocking problem. Like there was some permanent Exclusive lock on one or more system tables. Have you tried to look at 'sp_who' while Enterprise Manager is hung? If you see your EM SPID blocked by another SPID, try to find out what that SPID is doing.
//Hanslindgren
July 26, 2005 at 10:32 am
Check the "Auto Close" property on your databases. If auto close is enabled it will have to reopen every database everytime browse the databases (use use the database droplist in QA or expand the database tree in EM, etc.) . If you have a lot of databases this can be very slow.
If Auto Close is enabled disabled it on all of your DBs.
Mark
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply