Copying between databases
Data can be copied between two master databases, between a master database and a transportable database, or between two transportable databases.
A non current master database can be opened as a guest database for the purpose of copying data between master databases on the same machine or network.
A transportable database may be used for transferring data:
- Between databases within an organisation.
- When sharing data with external organisations.
- When sending data to Innovyze as part of a support request.
Notes:
- If you copy databases from the InfoWorks WS Pro version to the WS Pro for Info360 version, it does not copy checked in and checked out version controlled objects. A message window will appear detailing the items that will not be copied.
- You cannot copy databases from the cloud WS Pro for Info360 version to the InfoWorks WS Pro version - there is no Paste option.
Do not use Windows Explorer or File Explorer to copy databases
-
You should never copy a master database using Windows Explorer or File Explorer, rename the copy, and then carry on using the new and original databases.
-
You should never use the methods provided by the database application to copy a SQL Server database and then carry on using the new and original databases.
-
You should never use the methods provided by the database application to copy an Oracle database and then carry on using the new and original databases.
The only completely safe solution is to never, ever, copy master databases using Windows Explorer or File Explorer.
Every master database has a unique database identifier . When generated automatically, this identifier is a Globally Unique Identifier (GUIDA Globally Unique IDentifier, or GUID, is an automatically generated identifier that is guaranteed to be unique across all systems. It is generated using a complex algorithm based on the date and time and the individual computer's network card ID. GUIDs take the form {629810C2-3F6B-11D3-9BF3-00600891B690} and you will see them in a number of places where uniqueness is essential.). This identifier is used to manage files in the working folder, and in some circumstances files that form part of the master database itself.
If you work with two master 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 be based on the same root network, it could be difficult to spot that these problems are occurring.
