EM locks up

On certain occasions, when I'm running a long-running query in Query
Analyzer, I can't get in to Enterprise Manager. What happens is the list of
tables can't be enumerated until the long-running query finishes. What's
odd to me is that the query only affects 1 or 2 tables. So why can't I get
into EM until this job finishes?
Thanks, Andre
Hi,
This might be because your ISQLW.EXE in client machine will be using the
CPU and Memory fully. If you have better processor PIII or higher +
512 MB ram you should have such issues.
Check your virtual memory definition in your client machine. Always try to
run the long running queries in text result mode.
Thanks
Hari
MCDBA
"Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
news:#O07UKgLEHA.1556@.TK2MSFTNGP10.phx.gbl...
> On certain occasions, when I'm running a long-running query in Query
> Analyzer, I can't get in to Enterprise Manager. What happens is the list
of
> tables can't be enumerated until the long-running query finishes. What's
> odd to me is that the query only affects 1 or 2 tables. So why can't I
get
> into EM until this job finishes?
> Thanks, Andre
>
|||Actually, the long-running query is running on a different box. For
example, if you and I were in the same office, and I was running the query,
you might not be able to get into EM.
Andre
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23udrVlgLEHA.1032@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Hi,
> This might be because your ISQLW.EXE in client machine will be using the
> CPU and Memory fully. If you have better processor PIII or higher +
> 512 MB ram you should have such issues.
> Check your virtual memory definition in your client machine. Always try to
> run the long running queries in text result mode.
> Thanks
> Hari
> MCDBA
>
>
> "Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
> news:#O07UKgLEHA.1556@.TK2MSFTNGP10.phx.gbl...
list[vbcol=seagreen]
> of
What's
> get
>
|||Hi,
Means , you will be able to open the enterprise manager, but while expanding
your SQL Server it just hangs..
Can you check the SQLSERVR.exe CPU usage in server. If it is 100% then the
performance will be slow and cause a time out. The CPU usage in the log
running query can be minimized by tuning the query by effect sql statement
and adding proper indexes.
Did you installed SP3 in SQL server machine. If not install SP3.
Thanks
Hari
MCDBA
"Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
news:ep0$dzgLEHA.3292@.TK2MSFTNGP11.phx.gbl...
> Actually, the long-running query is running on a different box. For
> example, if you and I were in the same office, and I was running the
query,[vbcol=seagreen]
> you might not be able to get into EM.
> Andre
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23udrVlgLEHA.1032@.tk2msftngp13.phx.gbl...
the[vbcol=seagreen]
to[vbcol=seagreen]
> list
> What's
I
>
|||sp3a was installed shortly after it was released. Yes, I (or other users)
can launch EM, can expand the server, but can't get a list of tables when
trying to expand the tables folder. Query analyzer works just fine. CPU
usage on the server is typically low when this is happening. sp_who2 shows
that the long running query is blocking the EM process. I just can't figure
out why a query that "might" have a lock on a table would prevent the list
of tables from being displayed in EM.
Andre
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:ODjXezpLEHA.3052@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Means , you will be able to open the enterprise manager, but while
expanding[vbcol=seagreen]
> your SQL Server it just hangs..
> Can you check the SQLSERVR.exe CPU usage in server. If it is 100% then the
> performance will be slow and cause a time out. The CPU usage in the log
> running query can be minimized by tuning the query by effect sql statement
> and adding proper indexes.
> Did you installed SP3 in SQL server machine. If not install SP3.
> Thanks
> Hari
> MCDBA
> "Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
> news:ep0$dzgLEHA.3292@.TK2MSFTNGP11.phx.gbl...
> query,
> the
try[vbcol=seagreen]
> to
can't
> I
>
|||Hi,
Do you have the problem yet? I am having a similar problem. I have 2 machines:
1 .- SQL server 2000 + SP3, without problems
2 .- SQL Server 2000 + SP3a, with performance problems
I am reinstalling Sql server + SP3 and I am testing machine 1. I am sending you information.
Lina
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

EM locking on 7.0 restore database

When I try to retore a database on my 7.0 server, EM locks
up and quits responding.
On my workstation, I have EM2000, which I know is a
problem (thanks to KB # 312537) but the same thing happens
when I try it using he version of EM that is on that
server.
(I guess I'm assuming that EM is 7.0, is there a way to
check?)
Any other ideas? Thanks MarkHi Mark.
If you see the SQL Enterprise Manager hanging, don't assume that the server
(often another physical computer) is not actually performing any work.When
I'm restoring a db & wondering how it's going, I generally just monitor
something simple, such as CPU usage for the SPID that's controlling the
restore task to ensure that the server is actually performing work.
If you're technically minded / interested, the SQL Enterprise Manager is a
Microsoft Management Console (MMC) SnapIn type application. MMC SnapIns run
within the MMC Console process, which itself provides only a single thread
for managing all of it's SnapIns. If a dialog in a SnapIn such as the backup
restore is designed to "hang", waiting for a response from a server
application (such as SQL Server), the problem is that it doesn't allow the
user to continue interacting with other aspects of the SnapIn. Even worse,
the MMC Console might have other management SnapIns loaded (right click on
"My Computer" & select "Manage", then expand "Services and Applications" for
an example of a console where many SnapIns are loaded into a single
Console). If one hangs the MMC Console thread (such as the SQL Restore
dialog), all SnapIns are hung along with it! This can be bad if the other
SnapIns are doing something important.
That was a bit of a rant, but basically, this is why I avoid using the SQL
7.0 EM restore dialog like the plague - it hangs the GUI SnapIn Console. If
you simply use the RESTORE command from Query Analyser, you get
informational progress messages which at least let you know how things are
going.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Mark Hoyt" <mhoyt@.affiliatedhealth.org> wrote in message
news:061701c38d1a$e5f942d0$a301280a@.phx.gbl...
> When I try to retore a database on my 7.0 server, EM locks
> up and quits responding.
> On my workstation, I have EM2000, which I know is a
> problem (thanks to KB # 312537) but the same thing happens
> when I try it using he version of EM that is on that
> server.
> (I guess I'm assuming that EM is 7.0, is there a way to
> check?)
> Any other ideas? Thanks Mark|||Thanks Greg,
This turned out to be exactly the problem, I was just too
quick to assume "not responding" meant I had a problem.
Starting the process, going out to breakfast, and coming
back was all it took.
Thanks for the help!
>--Original Message--
>Hi Mark.
>If you see the SQL Enterprise Manager hanging, don't
assume that the server
>(often another physical computer) is not actually
performing any work.