# ERP Database Growth and Archive Savings Calculator

> Source: https://netray.co/tools/legacy-erp-database-growth-and-archive-savings-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Projects database size forward, applies an archive share and prices the storage and backup copies you avoid.

## Category

erp-operations

## Erp

Microsoft Dynamics GP

## Audience

- DBA
- IT manager
- ERP administrator

## Tool

**Kind:** calculator

**Currency:** $

**Inputs:**

#### Current database size

**Key:** db_gb

**Type:** number

**Default:** 400

**Min:** 1

**Step:** 10

**Unit:** GB

#### Annual growth

**Key:** growth

**Type:** slider

**Default:** 18

**Min:** 0

**Max:** 80

**Step:** 1

**Unit:** %

#### Years to project

**Key:** years

**Type:** slider

**Default:** 5

**Min:** 1

**Max:** 10

**Step:** 1

**Unit:** years

#### Share of data archivable

**Key:** archive

**Type:** slider

**Default:** 55

**Min:** 0

**Max:** 95

**Step:** 5

**Unit:** %

**Help:** Closed history older than your reporting and audit need.

#### Copies kept (prod, backup, DR, test)

**Key:** copies

**Type:** number

**Default:** 4

**Min:** 1

**Step:** 1

**Unit:** copies

#### Storage cost

**Key:** cost_gb

**Type:** number

**Default:** 0.25

**Min:** 0

**Step:** 0.05

**Unit:** per GB/month

**Outputs:**

#### Projected size

**Key:** size_future

**Expr:** db_gb * pow(1 + growth / 100, years)

**Format:** number

**Description:** Size in GB at the end of the horizon.

#### Archived volume

**Key:** archived_gb

**Expr:** size_future * archive / 100

**Format:** number

#### Remaining live size

**Key:** remaining_gb

**Expr:** size_future - archived_gb

**Format:** number

#### Annual storage cost without archive

**Key:** cost_without

**Expr:** size_future * copies * cost_gb * 12

**Format:** currency

#### Annual storage cost with archive

**Key:** cost_with

**Expr:** remaining_gb * copies * cost_gb * 12

**Format:** currency

#### Annual saving

**Key:** saving

**Expr:** cost_without - cost_with

**Format:** currency

**Primary:** true

**Chart:**

#### Annual saving vs archive share

**Type:** line

**X:** archive

**From:** 0

**To:** 90

**Steps:** 19

**Series:**

- saving

**Disclaimer:** Storage cost alone understates the benefit: smaller databases also back up, restore and migrate faster.

## Content

**Intro:** Large legacy databases slow backups, upgrades and migrations. Archiving closed history trims all of those. This calculator sizes the storage side of the benefit.

**Sections:**

#### How to use it

**Body:** Read the current size from SQL Server, then use the growth over the last two years rather than a guess. For archivable share, look at closed sales, purchasing and inventory history older than your reporting window. Count every copy that sits on paid storage, including backups, disaster recovery replicas and test refreshes.

#### The method

**Body:** Projected size equals current size times one plus growth raised to the years. Archived volume is the archive share of that size, and the live remainder is the rest. Annual cost is size times copies times monthly price times 12. Saving is cost without archive minus cost with archive.

#### What to watch

**Body:** Archive only what you can still retrieve for audit and tax. Legal retention periods differ by country, so confirm with your advisers. Test that archived data remains readable after a future migration, and keep a documented index. The biggest mistake is purging rather than archiving data that regulators may later request.

**Bullets:**

- Confirm retention rules
- Keep archived data readable
- Test restores
- Measure faster migration loads

**Cta:** Netray can build private search over archived ERP data so history stays answerable without keeping it live. You can use the calculator without that.

**Faq:**

#### How fast do GP or AX databases grow?

**Answer:** It depends on transaction volume, attachments and logging. Measure your own growth over a year from backup sizes, which is more reliable than a rule of thumb.

#### Is archiving the same as deleting?

**Answer:** No. Archiving moves data to cheaper, read-only storage while keeping it retrievable. Deleting removes it. Use deletion only where retention rules allow.

#### Does a smaller database speed up migration?

**Answer:** Usually yes, since less data must be extracted, transformed and validated. Loading closed history separately or not at all is a common way to shorten cutover.

#### Why count copies?

**Answer:** Because every backup, replica and test copy consumes storage. Four copies means each saved gigabyte is saved four times.

## Search terms

gp database size growth, dynamics gp archive old data, ax database growth archive, erp data archiving savings, sql server erp database growth, legacy erp data retention cost

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json