locked
Database Size RRS feed

  • Question

  • Hi,

    I was just wondering what you guys were seeing as a normal database size for your CRM Orgs?

    My internal deployment has grown to be about 60GB in size. Wondering if you guys knew of any CRM best practices when it comes to large databases?

    Keir
    Thursday, August 13, 2009 10:30 AM

Answers

  • As long as you continue to add records, the DB will continue to grow.  If perf is a concern, then you should look at where you might be havng poor query performance.  Typically, this will be realted to the Quick find fucntionality on the grids as the queries are not optimized that well and you may not have created needed indexes.  Once you have a record though, the DB size doesn't impact overall system response much since the access is more optimized.

    You might want to review record counts to find out where your larger tables are and then determine if you need to consider adding some sort of purge/archive processing to the system.  However, removing records could reduce the effectiveness of having a CRM system in the first place.

    Also, attachements are often a key factor in a large DB.  If you have large numbers of atttachements and the annotation table is large, then the size probably isn't impacting overall perf by a huge amount.
    Matt, MVP - Dynamics CRM
    Friday, August 14, 2009 8:09 PM

All replies

  • Hi, Keir.

    Try to shrink database and transaction log files.
    Truth is opened the prepared mind My blog - http://a33ik.blogspot.com
    Thursday, August 13, 2009 10:50 AM
    Moderator
  • Hi, Keir.

    Try to shrink database and transaction log files.
    Truth is opened the prepared mind My blog - http://a33ik.blogspot.com

    create a sql job shrinking the transaction logs perodicaly.
    I am building a 150 GB CRM db and I created this job,works like a bomb

    Tiaan van Niekerk http://crmdelacreme.blogspot.com Skype:tiaan.van.niekerk1
    Thursday, August 13, 2009 10:58 AM
  • The 60GB database has minimal free space in it, it's mostly data. I have maintenance plans that run daily to shrink and truncate the log files and data files of the database.

    My question was more to do with when you do have a large database that is all data, how do you deal with it? Does it effect performance? Microsoft recommend databases be a maximum of 50gb for performance reasons.

    Does CRM just keep growing and growing indefinately?

    Keir

    Thursday, August 13, 2009 11:10 AM
  • Your hardware archtecture will be the only draw back on growiing db's.
    Thats i why when you degsin or customize CRM stay with the relational db desgin and not storing the same data all over.


    Tiaan van Niekerk http://crmdelacreme.blogspot.com Skype:tiaan.van.niekerk1
    Thursday, August 13, 2009 11:28 AM
  • As long as you continue to add records, the DB will continue to grow.  If perf is a concern, then you should look at where you might be havng poor query performance.  Typically, this will be realted to the Quick find fucntionality on the grids as the queries are not optimized that well and you may not have created needed indexes.  Once you have a record though, the DB size doesn't impact overall system response much since the access is more optimized.

    You might want to review record counts to find out where your larger tables are and then determine if you need to consider adding some sort of purge/archive processing to the system.  However, removing records could reduce the effectiveness of having a CRM system in the first place.

    Also, attachements are often a key factor in a large DB.  If you have large numbers of atttachements and the annotation table is large, then the size probably isn't impacting overall perf by a huge amount.
    Matt, MVP - Dynamics CRM
    Friday, August 14, 2009 8:09 PM