|
|
Posted by sql_server_user on 05/17/06 19:49
I have a loading process that periodically inserts a lot of relatively
large files (up to 400MB) into a few substantial tables (about 50GB).
Sometimes, after inserting many files with no problem, the DB server
memory usage will suddenly jump from about 4.5GB to about 5.5GB (the
server has 4GB physical), the normally heavy disk activity will stop,
and the normally low CPU utilization will spike to about 90%, and stay
there, and the DB will become totally unresponsive to any connection
attempt - sqlcmd dedicated admin connections included.
Has anyone seen this before? Does anyone have any idea what it might
be, or how I can avoid it? If I kill the sqlserver process and start it
up again, which entails a lengthy recovery process, I incur an
unacceptable service outage.
Thanks,
Seth
Navigation:
[Reply to this message]
|