Hope you can help.
We have a new 64-bit Win 2003 SP2 server, with SQL Server 2005 SP3 installed.
Running for a few weeks and we are performing some test migrations.
Tets maintenance plans were created last week and the integrity check on one db ran on Sat 15th 10:00am. This completed successfully at 10:05am.
Using our Idera Diagnostics Manager I have noticed today that the SQL Memory Used is over 75% constantly. I have gone back through the history viewer and it was recorded at 10:06am on Sat 15th that Memory Jumped from 40% to 75%, at that time Disk Queue length for G (data drive) also spiked to 623.
I have checked logs, event viewing and nothing showing up apart from the above dbcc command that completed as stated. At 10:06 when this state change was repoted there were no active or user sessions on the server at all.
Disk queue length dropped back to normal by 10:12 the next snapshot from Idera, but memory is still at 75%.
Not sure what has caused this? any idea anyone?
We are migrating our Prod dbs over next week and need to know what has caused this.