Enterprise Manager Hangs

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 issue.
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
*** Sent via Developersdex http://www.developersdex.com ***Can you try executing this sp from QA and tell us how much time it takes?
exec master.dbo.sp_MShasdbaccess
AMB
"Art" wrote:
> 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 issue.
> 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
>
> *** Sent via Developersdex http://www.developersdex.com ***
>|||May be what Erdal is saying, is what is hurting the sp. Try executing the
only statement inside the sp [sp_mshasdbaccess] and you will get same
problem, but if you comment the line:
-- owner = substring(suser_sname(sid), 1, 24),
then everything will be normal.
Try reporting this to Microsoft.
AMB
"Art" wrote:
> We have about 20 databases. Thing is, we had absolutely no problems
> until we moved to this new environment (Windows / AD) a few days ago -
> Looks like this may be an access/permissions issue? I looked at the
> autoclose option for a couple of the databases on the server and looks
> like it is false (I used SELECT DATABASEPROPERTYEX('<DBNAME>',
> 'IsAutoClose')).
> Thank you!
> Artie
>
> *** Sent via Developersdex http://www.developersdex.com ***
>