Restoring K2.net™ to its default configuration without running the 'WipeInst' and 'WipeLog' stored procedures
KB000045
PRODUCTK2.net 2003
TAGSInstallation
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
In a development or testing environment, it is sometimes favorable to restore the system to its default installation configuration. By having a backup configuration available, it is simple and easy to revert to a default configuration.
| In a development or testing environment, one can revert to a default configuration if one has a backup configuration available to restore. Steps: | ||||
| 1. | Immediately after a clean installation create a backup of the K2.net™ 2003 databases. The K2.net™ 2003 databases are "K2" and "K2Log". | |||
| 2. | Ensure that the K2.net™ 2003 Server Service is not running. | |||
| 3. | Make use of Microsoft SQL Server Enterprise Manager to make a backup of these 2 databases. | |||
| 4. | Store these backups in a safe place. | |||
| Steps: | ||||
| 1. | Stop the K2.net™ 2003 Server Service. | |||
| 2. | Make use of Microsoft SQL Server Enterprise Manager to restore the backup databases created previously. | |||
| 3. | Start the K2.net™ 2003 Server Service. The default installation configuration should now be available. | |||
| 4. | Export all your processes to K2.net™ 2003 Server. | |||
| ||||
