You can move a Standard database to a new location if needed. You must copy the database file and the additional file data for the database to work correctly.
With an Oracle or SQL Server database, you can move the Remote Root directories to a new location and then change your Remote Roots to point at the new locations. See File Locations for more details on what files make up the database.
Every database has a Unique Database Identifier used to manage files in the local folders, and in some circumstances, files that form part of the database itself.
If you work with two databases that have the same Unique Database Identifier your working files will get mixed up and you run a very real risk of losing or corrupting data. Because your working copies of networks may well be based on the same root network, it could be difficult to spot that these problems are occurring.
The correct way to copy data, is to create a new database, and then open the existing database as a guest to copy data from. Alternatively, use a transportable database to transfer data from the old to the new database. This approach is designed to:
- let you copy data into a new database or an existing database that already contains data
- protect the integrity of the data in both databases
- support copying data between on-premise databases of different types
See Copying Data Between Databases for further information.