March 3, 2016 at 12:47 am
Goodmorning
due to the fact that we did not have space in one DB we add 50GB in order to increase the space. today i check the space in DB and I saw that was about 40GB ( 10GB less from the 50GB).
I wiil appreciate if you tell me how can i find the jobs ( or anything else, backups, FILES) that were running last night and the db was reduced 10gb.
is there any script to find any unused or other backups, files in order to delete
ALSO COULD YOU SUGGEST ANYTHING IN order to increase the available size of the db.
thanks in advance
March 3, 2016 at 2:41 am
Are your databases in Full recovery model? If they are, have you taken any log backups?
March 3, 2016 at 3:07 am
the recovery model is simple and it takes full backup
March 3, 2016 at 3:28 am
Hi,
is the mdf bigger, or the ldf file?
Can you check you scheduler, if there are some maintenance jobs like index-rebuild? Is there some replication, or mirroring?
What is the result of
dbcc sqlperf (logspace)
Kind regards,
Andreas
March 3, 2016 at 6:30 am
Data is going to grow. You need to be prepared for that. If you want to monitor what's happening on a database, the best tool is extended events. However, you have to set it up ahead of time. You can't retroactively go back in time to figure what happened when you didn't have monitoring set up.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 3, 2016 at 7:32 am
+1 for Grant's note. You will see data growth, which sometimes is unexpected. New indexes can account for this, loads, ETL, etc.
Extended Events will help, but it can be a lot of data to go through.
However do implement some kind of monitoring to look at whether you are growing from data, logs, or something else.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply