Notifications
Clear all
General Discussion
3
Posts
3
Users
0
Reactions
85
Views
Topic starter
A while back I asked a question about backup sizes, especially one in particular after an upgrade. I noticed last week that my Backup size grew by 7GB overnight. I was sort of thinking it may drop down again but that doesn't seem to be happening other than a 2GB drop the next day. We certainly could not have contributed 7GB to the database in a day as our normal average growth is. It does not seem to be a problem and I have the space (for now) but as the DB keeps growing it makes the transfer of data to my backup devices longer and the long term storage more expensive. This has only happened twice before so it shouldn't be an issue but I do like to understand what goes on with stuff like this. All of my maintenance jobs are running and did run on these dates and patch Tuesday updates were not applied until the weekend to avoid a backup-interrupting reboot.
02/19/2018 04:39 AM 96,498,392,576 CentricityPS_db_201802190359.BAK
02/20/2018 05:13 AM 96,543,384,576 CentricityPS_db_201802200436.BAK
02/21/2018 03:58 AM 103,381,887,488 CentricityPS_db_201802210318.BAK
02/22/2018 04:49 AM 101,699,295,744 CentricityPS_db_201802220338.BAK
02/23/2018 05:32 AM 101,800,698,880 CentricityPS_db_201802230450.BAK
I am certain a lot of clinics have much bigger databases and bigger challenges. I have the space for now and I will be building new servers for my next upgrade and need to try to guesstimate what kind of space I will need for the backup volume
Mike Zavolas
Tallahassee Neurological Clinic
Posted : March 2, 2018 2:12 am
Could be a # of things--
- Autogrow settings for data and log file kicking in.
- Reindexing job possibly rebuilt / reorganized an index increasing space consumed.
- Is your database set to full recovery? Do you have transaction log backup jobs configured?
I've seen similiar growth in our database but it's always associated with the log file and something causing a high amount of change (maintenance tasks or an upgrade)- I've never seen a 7GB increase in the data file over night.
Tracking the change now will be difficult since it already happened but there are a few SQL agent jobs out there that seem easy enough to setup- will write file size details to a temp table on a schedule and can be queried for historically reviewing file size.
- Jon
Posted : March 2, 2018 4:34 am
Also CQR and ePrescribing can add to the database. Any scheduled tasks doing CQR fixes, etc?
Posted : March 2, 2018 12:26 pm
