I recently did a backup and noticed the zip file was about 1 gig big.
Is there a way to run something to compact the db or is this it ?
I'm currently running Version 5.2.0j (Build 5804) of the community edition.
I recently did a backup and noticed the zip file was about 1 gig big.
Is there a way to run something to compact the db or is this it ?
I'm currently running Version 5.2.0j (Build 5804) of the community edition.
Sugar data don't uses to be very big, once attachments are all stored on server file system instead on database.
Whether your database backup are really big, I can think in two options:
1. You really have a lot of data and it can't be reduced.
2. You could take a look on tracking table, it uses to be sugar biggest table cause it logs all user's actions, but its data are unnneed in a genneral way. So you would make a backup skipping this table data to check the reducing of your backup size.
Rafael Queiroz Gonçalves
Advanced OMG UML Certified Professional
Sun Certified Enterprise Architect for the Java Platform
Sun Certified Programmer for the Java 2 Platform
IBM Certified Advanced Application Developer - Lotus Notes and Domino
IBM Certified Application Developer - IBM WebSphere Portlet Factory
Computer Science Mastering / UFSC - PPGCC
Side note: this is one of the reasons why you should always backup the sugar file system too. Another really important reason is that every change in admin section of Sugar changes the Sugar source code / configuration files and in some cases the database structure too and both parts must fit together.
Stefan Ulrich Sauer
System Analyst
Devoteam Danet GmbH
Gutenbergstraße 10
D-64331 Weiterstadt
Germany
email: Stefan-Ulrich.Sauer@devoteam.com
http://www.devoteam.de
The pruning job in the Sugar scheduler should be compacting it for you, assuming it is actually running. You can check it by looking at Admin > Schedulers.
Also, if you are on MS-SQL, you might want to try truncating the database's transaction log.
Lastly, is the 1 GB you mention a reference to the database or the program files? If the latter, it could be the result of a lot of attachments, either for email, notes or documents. It could also be the result of multiple uses of the Diagnostics Tools in the Admin control panel. That process makes a copy of the files one chooses to download and unless they are deleted, they remain within the directory structure of Sugar. I've seen that cause large bloats as well.
Regards,
Angel Magaña
Co-Author: Implementing SugarCRM 5.x (Packt Publishing -- Sept. 2010)
Blog: http://cheleguanaco.blogspot.com.
Twitter: @cheleguanaco.
________
| Projects: |_____________________________________
|
| CandyWrapper (.NET Wrapper for SugarCRM SOAP API). Source now available on GitHub!
| GoldMine to SugarCRM Express Conversion. Latest: 1.0.1.7 (Nov. 3, 2009)
| CRM SkyDialer (Skype Integration). Latest: 1.0.2 (Feb. 17, 2010)
| Round Robin Leads Assignment
| Phone Number Formatter
| CaseTwit (Twitter Integration)
______________________________________________
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks