Hi,
I have a large table in which an indexing operation initiated through
Enterprise Manager was interupted due to the server getting rebooted. Now
when I access Enterprise manager the memory usage for SQL Server goes very
high (almost 2 Gig) and Enterprise Manager does not respond. How I can I
start to resolve the issue of the high memory and Enterprise Manager not
responding?On Mon, 7 Nov 2005 15:12:02 -0800, Joe <Joe@.discussions.microsoft.com>
wrote:
>I have a large table in which an indexing operation initiated through
>Enterprise Manager was interupted due to the server getting rebooted. Now
>when I access Enterprise manager the memory usage for SQL Server goes very
>high (almost 2 Gig) and Enterprise Manager does not respond. How I can I
>start to resolve the issue of the high memory and Enterprise Manager not
>responding?
With luck, it was rolling back that interrupted transaction, and is
already back to normal!
How large was the table? Did you reboot the server because the
transaction was taking too long?
J.
Sunday, March 11, 2012
Enterprise Manager not responding
Labels:
database,
due,
enterprise,
indexing,
initiated,
interupted,
manager,
microsoft,
mysql,
nowwhen,
operation,
oracle,
rebooted,
responding,
server,
sql,
table,
throughenterprise
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment