Clear out MSDB file in sql server
I just joined a project which is live for the last 4 - 5 years.
This project is using SQL SERVER 2012 and on the server it has around 1500 databases.
I am noticing that SQL Server is consuming all the assigned memory (which is around 40GB).
Many time Transactions or query are getting timeout by SQL Server these days.
I checked and found that msdb file has grown to 68 GB in size. I am not sure that this is causing all these slow ness.
I tried to run the maintenance plan to clear out msdb but it just did not get ended. I tried it to run for two full days but then also it did not finished.
What I need to know is how can I clear this MSDB and is it one of the reason of this memory consumption by SQL Server
This project is using SQL SERVER 2012 and on the server it has around 1500 databases.
I am noticing that SQL Server is consuming all the assigned memory (which is around 40GB).
Many time Transactions or query are getting timeout by SQL Server these days.
I checked and found that msdb file has grown to 68 GB in size. I am not sure that this is causing all these slow ness.
I tried to run the maintenance plan to clear out msdb but it just did not get ended. I tried it to run for two full days but then also it did not finished.
What I need to know is how can I clear this MSDB and is it one of the reason of this memory consumption by SQL Server
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
That's the expected behavior even a minimum of 8GB should be reserved for the operating system.
You might need to add more memory or a better solution is to build a 2nd SQL Server box and migrate some of the databases there.
Is not. How much of those 68GB is data and how much is transaction log?
Which maintenance plan are you running? What you should do is to configure the SQL Agent to keep a shorter period of jobs history since having 1500 databases it should produce a lot of lines for each maintenance task, for sure. And not counting with each database specific job from their respective applications.