Remote SQL Server and 4.0 -> 4.5 Console Upgrade

We upgraded from SEC 4 to SEC 45 and are using a remote SQL 2005 X64 SP3 Server (not express) and all the databases are running in the 'default' instance.

We also received the same warning during the upgrade...

"Non-Sophos databases have been added to the SOPHOS instance. Applications relying on these databases may stop working after the upgrade. The non-Sophos databases detected are: *****, *****, *****,Warning"

The upgrade advisor KB article lists the following:

"Any work performed on the SOPHOS SQL instance has the potential to affect another applications that are using the SOPHOS instance.

For instance, if your SOPHOS instance is in MSDE format, this instance will be upgraded to SQL Server Express 2008 during the upgrade. We cannot guarantee that your other applications will be unaffected by this upgrade, so we urge you to check with the other software applications' vendors before proceeding.

If you are required to use a single SQL instance to host all of your databases, it is advisable to use an instance name other than SOPHOS so assumptions are not made by the installer."

However we were running the SOPHOS4 DB in the 'Default' SQL instance and not a 'SOPHOS' instance.

Knowing we had all the DB's recently backed up minutes prior to the upgrade and had taken snapshots of the VM environment, we ignored the warning and carried on with the upgrade.

We hit a couple of other minor snags which weren't related to the SQL DB and the upgrade completed without any errors.

The end result in SQL was two DB's  - Sophos4 and Sophos45, with the Sophos45 DB being used by Sophos.

I haven't removed the old Sophos4 DB as yet.

Apart from this and the fact that the upgrade process started a timer which counted down over 900 seconds, the upgrade went well. - Even with the errors messages.

Backup, Backup, Backup. Cross fingers and Good luck!

John

We upgraded from SEC 4 to SEC 45 and are using a remote SQL 2005 X64 SP3 Server (not express) and all the databases are running in the 'default' instance.

We also received the same warning during the upgrade...

"Non-Sophos databases have been added to the SOPHOS instance. Applications relying on these databases may stop working after the upgrade. The non-Sophos databases detected are: *****, *****, *****,Warning"

The upgrade advisor KB article lists the following:

"Any work performed on the SOPHOS SQL instance has the potential to affect another applications that are using the SOPHOS instance.

For instance, if your SOPHOS instance is in MSDE format, this instance will be upgraded to SQL Server Express 2008 during the upgrade. We cannot guarantee that your other applications will be unaffected by this upgrade, so we urge you to check with the other software applications' vendors before proceeding.

If you are required to use a single SQL instance to host all of your databases, it is advisable to use an instance name other than SOPHOS so assumptions are not made by the installer."

However we were running the SOPHOS4 DB in the 'Default' SQL instance and not a 'SOPHOS' instance.

Knowing we had all the DB's recently backed up minutes prior to the upgrade and had taken snapshots of the VM environment, we ignored the warning and carried on with the upgrade.

We hit a couple of other minor snags which weren't related to the SQL DB and the upgrade completed without any errors.

The end result in SQL was two DB's  - Sophos4 and Sophos45, with the Sophos45 DB being used by Sophos.

I haven't removed the old Sophos4 DB as yet.

Apart from this and the fact that the upgrade process started a timer which counted down over 900 seconds, the upgrade went well. - Even with the errors messages.

Backup, Backup, Backup. Cross fingers and Good luck!

John