web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Recommended size of company databases

(0) ShareShare
ReportReport
Posted on by

I asked this question of a couple people a few years ago at Convergence, but I'd like to see what the rest of the community has to say.  Is there a recommended size that a company database should stay below?  When I asked at Convergence, most databases seemed to be below 10GB; ours is significantly over that.

Thanks

*This post is locked for comments

I have the same question (0)
  • Frank Hamelly | MVP, MCP, CSA Profile Picture
    46,615 Super User 2025 Season 2 on at
    RE: Recommended size of company databases

    That's a very cool query Jonathan.  Thanks!

  • Jonathan Fear Profile Picture
    on at
    RE: Recommended size of company databases

    Carl you have to remember that the more information you have a table the larger the database. This isn't just one table you are looking at but all of them. You can use the following script that will tell you how large each table is:

    SELECT [total size KB], B.rows, O.name

    FROM (select sum(convert(decimal(10,0),dpages)*8129/1024)

         [total size KB], id

    FROM sysindexes group by id)

         A INNER JOIN sysindexes B ON A.id = B.id and B.indid in (0,1)

    INNER JOIN sysobjects O ON B.id = O.id WHERE B.rows <> 0

    ORDER BY [total size KB] desc

  • Community Member Profile Picture
    on at
    RE: Recommended size of company databases

    Thanks for the input so far.  Heather,  is there a way to determine the number of records?

  • Heather Roggeveen Profile Picture
    9,146 on at
    RE: Recommended size of company databases

    I agree that size is not necessarily an issue.  I am working with one of my clients currently to archive some of their data.  They have been a GP site for 10+ years and have lots of one off customers.  This has meant the number of customer records grows and grows.  That slows down processes such as statements that query all customer records.

    So it is not necessarily about size, but maybe number of records attached to regular processes that can determine that it is time to archive.

  • Richard Wheeler Profile Picture
    75,848 Moderator on at
    RE: Recommended size of company databases

    There is no recommended size for a GP database. Many of our clients who have an ecommerce component will have a database of hundreds of gigabytes if not a terabyte. The real question is that space being taken up by useful data or not. Sometimes third party or custom triggers can create thousands of useless records. You would really need to analyze what is in your database and what can stay and what can go. Also, there are archiving products out there as well as SQL tuning techniques to keep your system running at optimum speeds.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans