This topic will explain the DriveWorks migration process, using the DriveWorks Migration Tool, and the steps you need to take to ensure a successful migration from earlier versions of DriveWorks.
Any versions prior to 10 SP3 are to be run on a separate machine.
DriveWorks 7 to 11 data will open and run in DriveWorks without the need to migrate the data.
Once the DriveWorks 7 to 11 data has been opened and saved in DriveWorks it cannot be opened in the previous version.
The last service pack released for this version was SP 8.
To find out the version you have installed please see the article How To: Determine the Version of DriveWorks.
Before you begin, there are a few things you need to know about the migration process.
The most important thing to remember is that migration does not create a new migrated copy of your data, it modifies the copy that you give to it. What this means is that if you need to run DriveWorks 6 and later versions of DriveWorks side-by-side, you must first use DriveWorks 6 to make a complete copy of your implementation, and make sure that it works. For help doing this, take a look at the How To: Copy a DriveWorks 6 Implementation guide.
Another important point is that the implementation you migrate should be a full working version, if any of the project files are missing or unavailable, the migration process will fail and attempt to rollback any changes.
Finally, during the migration, the migration wizard works on temporary copies of your files so that if the migration fails for any reason, the implementation is left in its original state. Because of this, you must make sure that the directory you choose for the migration wizard to store temporary files in has plenty of space - depending on the size of your implementation this could be anything from a dozen megabytes to a few hundred megabytes or even more for large groups.
The migration process is divided into a few steps:
|Step 1||Introduction to the migration process.|
|Step 2||Select the DriveWorks group to migrate, either by browsing for the group's Microsoft Access database, or for its Microsoft SQL Server database.|
|Step 3||Choose where to create the new DriveWorks group, by browsing for an individual group file location.|
Choose whether you want to migrate:
Choose whether you want to migrate released model information.
Choose the temporary folder in which the migration will be performed (all changes are made to temporary files so that changes can be properly rolled back if anything goes wrong)
|Step 5||Review your migration options before you migrate, if there are any missing design masters or project files, an error will be shown in the list and you won't be able to proceed.|
The migration process will start, and when completed, the "Finish" button will be enabled.
Click "Finish" to close the migration wizard.
With DriveWorks 6 new drawings were always stored with the parent model. From DriveWorks 7 you now have the ability to store drawings in a separate location to the parent model. If the relative path parameter for each drawing is blank, the drawing will be stored in the Default Specification Folder location (see General Settings).
In DriveWorks 6 control over which users could specify which projects was granted in Team Settings. From DriveWorks 7 this now administered through Security Settings in the task list.