Knowledge Base

Search Knowledge Base

KB #240064: Upgrading from SQL 2000 to SQL 2005 on an instance secured with Encryptionizer for SQL

Type: Information
Summary:
You have an SQL 2000 instance that is secured with Encryptionizer for SQL. You wish to upgrade the instance to SQL 2005. You will need to perform the following steps to successfully upgrade and have access to the encrypted data after this major SQL upgrade.
Additional Information:
NOTE: Encryptionizer for SQL Server version 2005.201 or later is supported on Microsoft SQL Server 2005. If you have an earlier version, you will need to upgrade Encryptionizer prior to upgrading your SQL instance to SQL 2005. If you have a current support plan, this upgrade is provided free of charge. If you are no longer covered by a support plan, contact NetLib for options to obtain an upgrade.When you upgrade your instance of SQL from SQL 2000 to SQL 2005, the upgrade will change the directory structure of the instance by default. This directory change interferes with a security feature of Encryptionizer which does not allow the movement of a secured SQL instance.

The instructions are slightly different if you had previously chosen to encrypt any of the system databases, such as Master. Note: Encrypted System databases may not be applicable in your case. System Databases are only encrypted by choice.

System Databases NOT Encrypted

  • Detach any encrypted databases from the instance to be upgraded. It is not necessary to decrypt them.
  • Stop the SQL Instance to be upgraded
  • Run the NetLib Admin Wizard (SECADMIN.EXE) to disable Encryptionizer from the SQL instance (make sure that you know the encryption key profile information before disabling)
  • Perform your upgrade to SQL 2005 according to instructions from Microsoft. Your encrypted databases will not be accessible during the upgrade. They will remain at Compatibility Level 80(SQL 2000) but will function on SQL 2005.
  • Run the NetLib Admin Wizard (SECADMIN.EXE) to enable Encryptionizer once more – make sure to use the identical Key profile information as before.
  • Start SQL to confirm that you have access to your databases.
  • If you wish to upgrade your encrypted databases to Compatibility Level 90 (SQL 2005), you can now do this using instructions from Microsoft.

System Databases ARE Encrypted

  • Detach any encrypted databases from the instance to be upgraded. It is not necessary to decrypt them. The exception is system databases such as master (see below)
  • Stop the SQL Instance to be upgraded
  • Temporarily decrypt any System databases such as Master, if they are encrypted. If they remain encrypted, SQL will not be able to start up to perform the upgrade.
  • Run the NetLib Admin Wizard (SECADMIN.EXE) to disable Encryptionizer from the SQL instance (make sure that you know the encryption key profile information before disabling)
  • Perform your upgrade to SQL 2005 according to instructions from Microsoft. Your encrypted databases will not be accessible during the upgrade. They will remain at Compatibility Level 80(SQL 2000) but will function on SQL 2005.
  • Run the Encrypt/Decrypt Wizard (SECNCRPT.EXE) to encrypt your system databases, if so desired. Remember to use the same Encryption Key Profile is set in the Admin Wizard below.
  • Run the NetLib Admin Wizard (SECADMIN.EXE) to enable Encryptionizer once more – make sure to use the identical Key profile information as before.
  • Start SQL to confirm that you have access to your databases.
  • If you wish to upgrade your encrypted non-system databases to Compatibility Level 90 (SQL 2005), you can now do this using instructions from Microsoft.
Top