We are running:
Microsoft SQL Server 2005 Standard - 9.00.4294.00 (X64)
Microsoft Windows Server 2003 R2 Enterprise x64
We have gigabit interface.
Today we copied a file (using robocopy) from our databaseserver to another server (backup-server). The copy was started from the backup-server and source were specified using UNC.
The copy were using about 20% of the bandwith (about 200Mbit).
During the copy, sql-server reported several errors, for example:
AppDomain 15 (mp.dbo[runtime].14) is marked for unload due to memory pressure.
The client was unable to reuse a session with SPID 75, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
***Stack Dump being sent to [PATH\SQLDump0005.txt Resource Monitor (0x1384) Worker 0x000000008000C1C0 appears to be non-yielding on Node 0. Memory freed: 0 KB. Approx CPU Used: kernel 15 ms, user 218 ms, Interval: 428541.
So to me it appears that sql-server crashed during a file copy.
We have 27 GB ram. With 24.5 GB dedicated to SQL-Server.
The files we copied were quite large, some over 50GB.
I found a similar issue about this:
Do you think the issue above could be the cause of the sql-server crash?
View Complete Post