# Infor LN Database Growth by Table Calculator

> Source: https://netray.co/tools/infor-ln-database-growth-by-table-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Estimate how fast the main LN 10.x transaction tables grow from your order volumes, and how many GB you need after N years.

## Category

infor-ln

## Erp

Infor LN

## Audience

- DBA
- ERP administrator
- Infrastructure engineer

## Tool

**Kind:** calculator

**Inputs:**

#### Sales order lines per year

**Key:** so

**Type:** number

**Default:** 120000

**Min:** 0

**Step:** 1000

**Unit:** lines

**Help:** Rows in tdsls401.

#### Purchase order lines per year

**Key:** po

**Type:** number

**Default:** 80000

**Min:** 0

**Step:** 1000

**Unit:** lines

**Help:** Rows in tdpur401.

#### Production orders per year

**Key:** prod

**Type:** number

**Default:** 15000

**Min:** 0

**Step:** 500

**Unit:** orders

**Help:** Rows in tisfc001.

#### Inventory transactions per order line

**Key:** inv

**Type:** number

**Default:** 3

**Min:** 0

**Step:** 0.5

**Unit:** rows

**Help:** Rows written to whinr110 per sales line, purchase line or production order (receipts, issues, transfers).

#### Finance postings per order line

**Key:** fin

**Type:** number

**Default:** 6

**Min:** 0

**Step:** 1

**Unit:** rows

**Help:** Rows written to tfgld106 per sales line, purchase line or production order, from integration postings and invoices.

#### Average row size

**Key:** row

**Type:** number

**Default:** 1200

**Min:** 100

**Step:** 100

**Unit:** bytes

**Help:** Assumption. Measure it from your database for these tables.

#### Index overhead factor

**Key:** idx

**Type:** number

**Default:** 1.6

**Min:** 1

**Step:** 0.1

**Unit:** x

**Help:** Total table plus index space divided by data space.

#### Number of companies

**Key:** cos

**Type:** number

**Default:** 1

**Min:** 1

**Step:** 1

**Unit:** companies

**Help:** Companies with similar volume. For uneven companies, run the calculator per company.

#### Years

**Key:** years

**Type:** slider

**Default:** 5

**Min:** 1

**Max:** 10

**Step:** 1

**Unit:** years

**Outputs:**

#### whinr110 rows per year

**Key:** inv_rows

**Expr:** (so + po + prod) * inv

**Format:** integer

#### tfgld106 rows per year

**Key:** fin_rows

**Expr:** (so + po + prod) * fin

**Format:** integer

#### Total rows per year (these tables)

**Key:** total_rows

**Expr:** so + po + prod + inv_rows + fin_rows

**Format:** integer

#### Growth per year

**Key:** gb_year

**Expr:** total_rows * row * idx / 1000000000 * cos

**Format:** decimal

**Primary:** true

**Description:** GB per year including indexes, all companies.

#### Growth after N years

**Key:** gb_total

**Expr:** gb_year * years

**Format:** decimal

**Primary:** true

**Description:** GB added over the selected number of years if nothing is archived.

#### Share from finance postings

**Key:** fin_share

**Expr:** fin_rows / total_rows * 100

**Format:** percent

**Chart:**

#### Cumulative growth (GB) over years

**Type:** line

**X:** years

**From:** 1

**To:** 10

**Steps:** 10

**Series:**

- gb_total

**Disclaimer:** Rows per order line and row size are assumptions; LN writes to many more tables than the four modelled here. Calibrate against row counts and sizes measured in your own database.

## Content

**Intro:** This calculator projects how much the high-volume transaction tables of Infor LN 10.x grow each year from your sales, purchase and production volumes. It covers sales order lines, purchase order lines, production orders, inventory transactions and finalized finance transactions, which together usually explain most of the growth.

**Sections:**

#### Tables modelled and why

**Body:** Most LN data growth comes from transactions, not master data. Each sales order line is a row in tdsls401 and each purchase order line a row in tdpur401; production orders live in tisfc001. Each of these generates several inventory transactions in whinr110 (inventory transactions by item and warehouse) and several finalized finance transactions in tfgld106. The physical table name adds the company number, so tdsls401 in company 100 is ttdsls401100 in the database.

**Bullets:**

- tdsls401: sales order lines
- tdpur401: purchase order lines
- tisfc001: production orders
- whinr110: inventory transactions by item and warehouse
- tfgld106: finalized transactions (general ledger)

#### How to measure your real row size and ratios

**Body:** Do not keep the 1,200 byte default. On SQL Server run sp_spaceused on ttdsls401100, twhinr110100 and ttfgld106100 and divide data size by row count; (data + index_size) divided by data gives the index factor. On Oracle, compare USER_SEGMENTS bytes for the table and its indexes with the row count from statistics. For the per-line ratios, count rows in whinr110 and tfgld106 for one closed year and divide by the order lines of the same year. Those two ratios drive most of the result, so measure them first.

#### Worked example

**Body:** With the defaults, 215,000 order lines and production orders per year create 645,000 whinr110 rows and 1,290,000 tfgld106 rows, about 2.15 million rows in total. At 1,200 bytes and an index factor of 1.6 that is about 4.1 GB per year for one company, and about 20.6 GB after five years. Finance postings are 60 percent of the rows, which is typical when integration postings are detailed per transaction.

#### Which tables to archive first

**Body:** Look at the biggest growers in your own measurement, usually tfgld106 and whinr110, then at history tables of sales and purchase. LN has archiving sessions per package that move closed data to an archive company and keep integrity; use them rather than deleting rows in SQL, which breaks reference counters and audit trails. Before archiving finance, confirm retention rules with your auditors and the fiscal periods that must stay online for reporting.

**Cta:** If you want people to ask LN questions in plain English against these tables without writing SQL, we can set that up on your own servers.

**Faq:**

#### Where do I find the full Infor LN table list and data dictionary?

**Answer:** Use the table definition sessions in LN Tools (Application Development, under the package VRC) or the table definitions published on docs.infor.com and in Infor's LN table reference documents for your release. Tables are named by package and module, such as tdsls for sales or whinr for inventory reporting.

#### Why is tfgld106 so large?

**Answer:** tfgld106 holds finalized general ledger transactions. Every integration posting from sales, purchase, warehousing and production lands there after finalization, often several lines per business transaction. Detailed integration mapping and frequent finalization runs increase its row count. It is usually the first finance table to consider for archiving.

#### Does the company number change table names?

**Answer:** Yes. In the database the logical table code gets a 't' prefix and the company number suffix, so whinr110 in company 100 is twhinr110100. Shared tables via logical table linking are stored once in the physical company, so do not count them for each logical company.

#### Is this growth estimate accurate?

**Answer:** It is a planning model with five tables and averaged ratios. It is accurate when you replace the defaults with ratios and row sizes measured from one closed year in your own database. Add a margin for other tables, audit trails and temporary tables.

## Search terms

infor ln tables, infor ln table list, infor ln data dictionary, infor ln database size, whinr110 table, tfgld106 table, tdsls401 table, infor ln archiving

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