Documentation
Getting Started
Data Grid
Modeling
Business Rules
Approvals
Users, Roles & Security
Administration
Integration & API
Migrating from MDS
Architecture
Documentation/Installation/Import Test Data

Import Test Data

Generate realistic demo data to explore Primentra without typing everything by hand. The PowerShell script generate-demo-data.ps1 creates models, entities, attributes and data rows directly in your database.

Run the script

  1. Open PowerShell as Administrator.
  2. Go to the scripts folder: cd "C:\Program Files\Primentra\scripts"
  3. Run .\generate-demo-data.ps1
  4. Answer the six prompts, or accept the defaults.
  5. Refresh the browser to see the new models and entities.

Settings

SettingDescriptionDefault
ModelsNumber of models to create (1–10)3
Entities per modelNumber of entities per model (1–8)4
Min recordsMinimum rows per entity (0–1,000,000)0
Max recordsMaximum rows per entity (0–1,000,000)50
Avg attributesAverage attributes per entity (1–30)Automatic, 4–8 per entity
Delete existing dataWipe everything first, or add on topNo, additive

Each entity gets a random row count between the minimum and the maximum. Pass the first five as parameters to skip their prompts:

.\generate-demo-data.ps1 -Models 2 -EntitiesPerModel 4 -MinRecords 100 -MaxRecords 5000 -AvgAttributes 10

The script is additive by default. It picks from ten built-in themes — Organisation, HR, Finance, Logistics, Sales, IT, Quality, Procurement, Marketing, Facilities — and avoids model names that already exist.

Performance

  • Entities under 5,000 rows are generated in PowerShell and inserted as SQL VALUES statements.
  • Entities of 5,000 rows and more are generated server-side with SQL CTEs, which is much faster.
  • Progress is printed every 10,000 rows.
  • 99,000 rows usually finish in under 30 seconds.

Disk space for large imports

Inserting millions of rows grows the transaction log, especially in Full recovery mode. Check these before a run of 500,000 rows or more:

  • Transaction log space — run DBCC SQLPERF(LOGSPACE) in SSMS. If space is tight, switch the database to Simple recovery temporarily, or schedule log backups during the import.
  • Data file spaceEntityRows and EntityValues grow with the row count. A million rows with ten attributes adds roughly 1–2 GB.
  • Disk usage during the run — watch it with SELECT * FROM sys.dm_db_file_space_usage. If the disk fills up mid-import, the script fails and leaves partial data behind.
Restart the Primentra service, or just refresh the browser, to see the generated models.

Ready to get started?

Start managing your master data with Primentra today.

View Pricing
Import Test Data | Installation | Docs | Primentra