Manual Update

(Last update of this topic: 08-28-2017)

Navigation:  Installation > Update >

Manual Update

(Last update of this topic: 08-28-2017)

Previous pageReturn to chapter overviewNext page

This chapter describes the procedure of a manual update in an existing environment. It particularly aims not to affect the running operations. The procedure described below enables the administrator to carry out an update successively and without any time pressure. The goal is to keep the steadyPRINT Database parallel. This means that all Clients combine to the new and parallel running database without any effect on older Clients.

 

Backup of the Existing Database

The first step is to restore the existing steadyPRINT Database. A backup is for example done via the Microsoft SQL Server Management Studio under [INSTANZNAME] > Databases > [STEADYPRINT DATENBANK] > Tasks > Back Up ....

 

Parallel Import of Backup

The previously created backup of the database now has to be imported again under a different name. This procedure can for example be performed via the Microsoft SQL Server Management Studio under [INSTANZNAME] > Databases > Restore Database. The use of a suffix describing the respective version is recommended:

Example (old database name): PrinterMap

Example (new database name): PrinterMap_510

 

Important

No Permission after Restoring the Database

               

After restoring the database, the permission for the SQL user may be lost.

 

Adjust the permissions according to the knowledgebase entry on www.steadyprint.com.

 

 

Update the steadyPRINT Database

The update of the steadyPRINT Database must be done analog to chapter Installing the Database. Enter the name of the restored database as database name on the interface and select the installation type upgrade. In the example above this would be the database PrinterMap_510.

 

Update of the Components

The update of the other components (steadyPRINT Center, steadyPRINT Agent etc.) is performed in line with chapter Installing the Program Components. It is a matter of choice to carry out an update or a new installation. Enter the restored database as a database name in the installation routine. In the example above this would be the database PrinterMap_510.

 

 

 

All information is provided without guarantee of completeness, accuracy and currentness.