Remote SQL Server and 4.0 -> 4.5 Console Upgrade

Hi,

Does the SOPHOS instance have other DBs in it ?

Are you using the default instance ?

e.g. if the instance is called SOPHOS, and you use another program such as backupexec and their files are in the SOPHOS instance, and we upgrade the instance itself (from say MSDE to 2005/2008), then backupexec may not work.  We cannot tell if the other program will still work, so the upgrade advisor has to say that..

OD

This is not MSDE or SQL Express this is the full version of Microsoft SQL Server 2005 Standard Edition on another server. There are no "instances" in the full SQL Server that I'm aware of. That's all related to one of the tweaks I had to make to get 4.0 running with a remote, full Microsoft SQL Server 2005. Here's my current DatabaseConnectionMS in the registry that actually WORKS:

Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS4;Data Source=SERVERNAME;

To get the database connection, I had to remove the "\INSTANCE" name that all the documentation talks about. The "Initial Catalog=SOPHOS4" is the database name and "Data Source=SERVERNAME" refers to only the name of my server.

You should be glad it warns as it beats banging your head against a wall when you don't have a backup of the other databases or the installer has pushed the MSDE instance to SQL 2008 and the other application sharing the instance breaks as this isn't supported by them.

The following KBA says why the Upgrade Advisor warns of this issue. 

http://www.sophos.com/support/knowledgebase/article/110883.html

IMPORTANT: In these messages, the term "SOPHOS" is in fact referring to the instance name where the SOPHOS4 database is located.
Sophos recommends that you backup databases before making any changes to your system.
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.

Hi,

I have the same problem like Dean.

So what happens when I start the setup on my seperate SQL Server 2005 Standard Edition 64bit SP2?

Or how can I update the Sophos4 DB manual without starting this setup on my productive database server?

Thanks,

bernd

---

Berndi wrote:

Or how can I update the Sophos4 DB manual without starting this setup on my productive database server?

---

See: /search?q= 3857

Hi Ruckus,

thanks for your answer but this article describes how to manual create a new Sophos Database.

I have to update my old Sophos4 Database to Sophos 4.5

Hi,

The upgrade works by creating a "empty" SOPHOS45 database, this should be done first in the upgrade step of a distributed install.  This is either created by running the installer on the machine or running installDB.  Once the "empty" SOPHOS45 database is created, you then run the installer on the management server machine, as part of this install the tool UpgradeDB.exe is called and moves the data from SOPHOS4 to SOPHOS45.

Thanks,

Jak

I'm not sure I understand all of this completely (as I have a local SQL database and it's also 95F/35C outside and no A/C ).

It sounds like the upgrade advisor does not correctly deal with the case of a remote database. I don't think that the upgrade would ever touch/upgrade the remote database server (how could it) so it should be safe to ignore this warning.

As to the upgrade process: InstallDB.bat installs the new SOPHOS45 database. Then UpgradeDB.exe is called to copy and upgrade the contents of the SOPHOS4 dtatbase to the SOPHOS45 database. In case you have to run this command manually you have to specify the -sourceVersion=4 switch (note that it is case sensitive).

Christian

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