How do I work with a test database alongside my production database in imos iX?
Build and test changes in a copy of your imos database, such as IMOS_DEMO. How to create one, keep folders separate and move changes to production in a controlled way.
Short answer: Create a copy of your production database, for example IMOS_DEMO, by restoring a production backup under a new name on the same SQL Server. Give the test environment its own folders for orders, CNC programs and exports, and switch between the two with a fixed script instead of by hand. Build and test changes in the test database; move them to production only once they work.
Applies to
- imos iX 2019 and newer (applied in practice with imos iX 2021 up to 2025)
- imos iX CAD, imos Organizer and Microsoft SQL Server (Express or Standard) with SQL Server Management Studio
- Integrations such as Proteus, and exports to cutting and CNC software
- Last reviewed: October 2026
Creating the test database
- Choose the SQL Server instance with your IT administrator; usually the production one, for example
SRV-SQL\IMOSSQL2022. - Make a full backup of the production database. See imos iX database backup and restore for how.
- Restore that backup under a new name. In SQL Server Management Studio, under Restore Database, enter a new destination database name, for example
IMOS_DEMO. - On the Files page, check that the database files (.mdf and .ldf) get their own file names.
- Point one PC to the test database and open an existing order to check that everything works.
Before you click OK, check the destination database name and the file names twice. Otherwise you may overwrite production with an older state.
Separate folders for the test environment
imos also writes files: drawings, CNC programs, cutting lists and exports. A copied database and a copied imos.ini still point to the production folders.
- Give orders their own folder, for example
I:\Test\Imorder, and set it asPROJECT_PATHin the imos.ini. Test orders then never overwrite production orders. - Send the test CNC output to its own folder. A test program must never reach the machine.
- Give cutting lists and the ERP exchange folders (such as
TRANSFERPATHandSIMXMLIN/OUT/ERROR) separate test folders, so cutting and ERP software don't pick up test orders. - Keep the library (
SYS) shared if you're only testing data in the database. If you're testing new DWGs, images or drawing templates, work in a copy, for exampleI:\Test\Library. - Use the same drive letter for both; only the path after
I:\differs.
Switching between production and test
- Close imos iX. A new database and new paths are only read at the next start.
- Run the script for the environment you want, for example a Test or Production shortcut on the desktop. Wood Intelligence supplies such a
.batscript; it sets the server, database and paths in the imos.ini. See Where is the imos.ini and what can I change? - Start imos iX and check in the imos iX opties (imos iX options) which server and database are active.
- Switch the imos Organizer to the same database if you manage master data or orders there.
- With an integration such as Proteus, check which database it reads; it can ask for the database when you import.
Moving changes to production in a controlled way
- Record what you change, why, and who does it.
- Build the change in the test database.
- Test with fixed reference orders: drawing, cutting list, labels, purchase list and CNC programs, compared with production.
- Back up the production database right before the transfer.
- Transfer only the approved items to production, or repeat the change there following your record.
- Open a reference order in production straight away and let the designers know.
Have every designer work with their own database account. The database change log (the DATACHANGELOG table) then shows who changed which item.
Keeping the test database up to date
A test database ages; after a few months a passed test says little.
- Refresh the test database at a fixed moment, for example every quarter or before a larger project.
- First move all approved changes to production. Anything that only exists in test disappears when you refresh.
- Restore a fresh production backup over
IMOS_DEMO. This time, overwriting is exactly the point. - Then check the folders again: the database holds the production settings once more.
- Always install imos updates or updates to your blueprint database in the test environment first.
Why this approach?
In imos iX everything hangs off the database: the drawing, the cutting list, the labels, purchasing and the CNC programs. A mistake in a value set or connector hits live orders immediately in production. In a copy of production the same mistake hurts no one, while you still test against your own articles, materials and machines.
For a major rebuild, such as moving to a new blueprint, we often run two databases side by side. The old one stays in production, the new one is filled and tested, and the switch happens at one agreed moment. In practice, things go wrong with the folders rather than the database: a test order landing in the production order folder, or a test program on the machine.
Common mistakes
- Overwriting the production database during the restore. Check the name and file names before you start.
- Sharing the order or CNC folder between test and production. Test files then end up in the workshop.
- Forgetting to switch back. A real order drawn in the test database doesn't exist in production.
Frequently asked questions
Does the test database count towards the 10 GB limit of SQL Server Express?
The 10 GB limit applies per database. Production and test can each be up to 10 GB. Do allow for twice the disk space and for the backups of both.
Can I switch without a script?
Yes. You can pick a database when imos iX starts, but only if automatic login is turned off in the imos iX settings. You then change the paths by hand.
Can Wood Intelligence supply the switching script?
Yes. We supply a .bat script per environment that sets the imos.ini for the chosen database and paths, for every user via %APPDATA%. Get in touch for a script tailored to your setup.
Further reading
- How do I back up the imos iX database and restore it?
- Where is the imos.ini and what can I change?
- Planning an imos iX implementation
- imos iX consultancy
More than one solution
Almost every question in this knowledge base has more than one solution. The best fit depends on your workflow, machinery and integrations. Not sure which applies to you, or are you using software we don't (yet) support? Feel free to email Wood Intelligence. We're happy to think along with any challenge.
imos is a trademark of imos AG. Wood Intelligence is an independent consultancy.