Notifications
Clear all
Topic starter
My database is growing too large.
any recommendation? has anyone have a similar problem in the past?
if yes: What did you do to release some space and increase performance simultaneously?
My current database size is 858GB.
compressed backup file size is 258GB
edit:
Have anyone tried index drop or rebuilt to take out fragmentation?
Posted : July 19, 2016 4:42 am
There are shrink DB commands in SQL that clean up log files, and drop empty tables
I will say that these did not work for me though, the DB's are just really getting that out of control with the new features.
Posted : July 19, 2016 5:29 am
Topic starter
I don't have my logs and database in the same place.
My logs are store on a completely different spindle, And i have read and heard that shrinking a database is detrimental to the performance of it.
Posted : July 19, 2016 5:33 am
there is really not much that can be done. As the previous post stated, the new features and just normal data collection will increase the size of the database. GE does not offer an archiving solution for any records that are over 7 years. Right now, we are responsible for every bit of data that is within the database.
Posted : July 19, 2016 6:17 am
Do you have the proper maintenance plans configured against your centricityps database? Transaction log backups to keep the log volume at a manageable size? Out of that 858GB how much of it is the actual log file versus data file?
Shrinking the data and log file are 'ok' as long as you treat it as a 1 time run AND the proper maintenance tasks are ran afterwards to rebuild indexes and check the integrity of the database. Shrinking should not be a part of a routine maintenance task against a database.
As for the index fragmentation you should have a weekly task run the eithers rebuilds or reorganizes indexes. Ola Hallengren has excellent maintenance plans to assist with this, may require some modifications but is a good starting point.
Posted : July 19, 2016 6:17 pm
We had large database problems as well. With no way to really reduce the size we ended up just increasing the drive space. In place upgrade of RAID Drives is pretty painless.
Posted : July 20, 2016 3:38 am
One thing that can make the database grow faster is Auditing. You might check the level of Auditing you have enabled and see if it is feasible to back off on any of it. Other than that, the above suggestions are all good ones. I'm assuming you on on CPS but your profile lists all products. If you are on Oracle, you can further divide your database data by moving individual tablespaces to other drives. I'd involve GE if you wanted to do that. Would require downtime.
Posted : July 20, 2016 3:53 am
Topic starter
I don't have the logs on the same place as the database.
logs are kept separated from the database and get backup daily and shrink every 2 days.
Posted : July 20, 2016 5:54 am
Topic starter
Do you use those script for maintenance purposes?
I download a few of them and was reading some of the lines. They are quite complex and some require a couple of tweaking before they can be used.
Posted : July 21, 2016 6:38 am
David,
Do you have any images in your DB? If so export those if possible. Mine is close to 800GB but the backup is about 130-140GB. I should add I've removed over 200GB of images from my database about 8 years ago and imported have into DM and the older have stored as flat files on the filesystem.
Posted : July 22, 2016 7:10 pm
Is this Oracle or MSSQL?
Posted : July 22, 2016 7:13 pm
Yes you want to know exactly what you are doing and why when doing a shrink or it can effect performance. It also only helps if you have open space in the database. i.e. data file or files is 800gb but only 700gb is used.
Posted : July 22, 2016 7:17 pm
Topic starter
how to remove the images out of it?
Posted : July 25, 2016 8:52 am
Topic starter
yes, david is CPS.
Posted : July 25, 2016 8:52 am
Topic starter
SQL
Posted : July 25, 2016 8:54 am
Page 1 / 3
Next
