Convert a Vertec version before 6.5 with Microsoft SQL Server

This article covers DB Konvert for Vertec versions before 6.5. For information on DB Konvert from Vertec version 6.5, see the article Database Convert .

In the case of a Vertec update, the database must be converted to the new version. This guide assumes that you have basic knowledge of Microsoft SQL Server administration.

To convert a Vertec database with MS SQL Server, a temporary database must be created on the SQL Server.

This can be done via the Copy Database task described below or alternatively by creating a new empty database and importing a backup.

• Open Microsoft SQL Server Management Studio and right-click on the current Vertec database. In the dialog that appears, select Window Tasks > Copy Database...
• A wizard will appear to assist you in backing up the database:
  • Under Source Database, specify the appropriate database. The backup type is Full, the backup is not selected.
  • Select Destination Hard Disk and specify the file name with the Add button. Remove all other entries.
• Right-click and select Restore files and file groups...
  • Destination to recover, in Database: Specify directly the name of the temporary database to be created.
  • Specify the source for the recovery, from medium: backup file. Check the box below for the backup set to be restored.
• Once this process is successfully completed, click Close and restart Microsoft SQL Server Management Studio. The temporary database is now visible.

• In order for the conversion to run smoothly, a DTS 2000 Runtime must be installed. Download the file at the following link: SQLServer2005_BC_x64.msi ). This must be installed on the computer where the Vertec Server installation is located. If it is missing, DB Konvert will get the error message invalid class string.
• If an error occurs during a convert to SQL Server, the source database should be restored: The convert also changes data in the source database. If you start the convert again without a new restore of the source, this can lead to problems afterwards.
• Start Vertec.DBConvert.exe, which is located in the Vertec installation directory (for versions before 6.4, start Vertec with the /DC parameter). The following window opens:

  

• The Target Database field should already be initialized with the default Vertec installation setting and point to the Vertec database of the SQL Server.
• For the source database information, copy the contents of the target database and set Databasename=vertectemp (or the name of the temporary SQL Server database).
• Deactivate the Inplace conversion checkbox. The Create tables and Copy data checkboxes must be selected.
• The Use SQL option must be enabled.
• The field Set version to should contain the first 3 digits of the new Vertec version (e.g. 6.7.0).
• The conversion of a Vertec database to Microsoft SQL Server supports the use of DTS (distributed transaction service) component. DTS is part of the MS SQL Server product from version 7 and allows faster data transfer between SQL Server databases. To use DTS, select DTS Datapump (MS SQL).
• By pressing the start button, the tables in the target database are deleted first and then created. Subsequently, the data is copied from the Vertectemp database to the Vertec database and converted to the new version.
  The convert window lists which table is currently being created/copied. Please check this list briefly after completion for security. Please let us know if you see any error messages there.
• After conversion, the Vertec Desktop App has to be started once. The temporary database vertectemp is no longer needed and can be deleted.

The database conversion may end with the following message:

Failed to update index statistix

Since version 6.3 Vertec tries to recalculate the index statistics by default. The error message appears due to a bug in MS SQL Server, which prevents the Vertecuser, who is not directly DBO (i.e. not only registered as db owner), from recalculating the index statistics in SQL Server.

Updated index statistics are important for performance. If the automatic update did not work during the conversion, please perform the update manually by calling

EXEC sp_updatestats;

For more information on the Index Statistics, see the article on the MS SQL Server .

Vertec can be started normally in any case, the data conversion has been completed successfully.