MSDE To SQL 2005 Standard

Hi,

Is it full blown SQL server?  It seems odd that you would have full blown SQL server on the same machine as the Sophos Management Server especially if the database plays host to other application databases.  In an ideal world the SOPHOS databases would reside in their own instance but you could:

1. Take a backup of the SOPHOS3 database: backupdb.bat in "\program files\sophos\enterprise console\DB" will do this but I assume you have SQL Server Management Studio installed on the macine also so you could use that.  Either way, as long as you end up with a file such as sophos3.bak

2. Create a new database called SOPHOS3 in the SQL Server 2005 instance.  Ideally choosing separte dedicated physical drive for the data and log files.  

3. Restore the backed up SOPHOS3 database into the new SOPHOS3 database in the SQL 2005 instance.

You can use RestoreDB.bat which can be found in the same localtion as Backupdb.bat, again you could use SQL Server Management Studio.

4. I would then suggest going through the properties of the new SOPHOS3 database and turn off auto shrink and autoclose.  Maybe take a look at: http://www.sophos.com/support/knowledgebase/article/111353.html.

5. Then you need to point the management service at the new instance and database rather than the MSDE one.  To do so:

5.1. Stop the Sophos Management Service.

5.2 Change the connection string that the Sophos Management Service uses.  You'll find it under DatabaseConnectionMS in: HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\EE\Management Tools\.

At the end of the connection string it has:

Data Source=

This should be updated to reflect the machine and the new instance name.

5,3 Also update: HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\EE\Management Tools\Database Installer\Instance to reflect the new instance name, if this is a "no named" instance then enter MSSQLSERVER.  If you don't change this the Sophos Upgrade Advisor will complain that you've moved the database outside of the installer.

5.4 Start the Sophos Management Service and open SEC, everything should be as you left it.

At this point you should still have the 2 instances but now the SEC 3 install is pointing at the SOPHOS3 database in the SQL 2005 instance.  Please ensure it's all working at this stage.  

I would then probably stop the service for the MSDE instance.  Run the Sophos Upgrade Advisor and check that it's happy.  If it complains about moving the database you might need to uninstall the MSDE instace of SOPHOS, I can't remember quite what it checks.  I believe it just reads in both of the above registry keys and checks that they match.  It might check for a SOPHOS instance being installed as well or that MSDE is installed.  If you can leave the MSDE uninstall to after the upgrade to SEC 4 and then SEC 4.5 that would be safer but if it is required to be removed to do the upgrade to SEC 4 then it should be fine.

I hope this helps.

Regards,

Jak

Hi,

Is it full blown SQL server?  It seems odd that you would have full blown SQL server on the same machine as the Sophos Management Server especially if the database plays host to other application databases.  In an ideal world the SOPHOS databases would reside in their own instance but you could:

1. Take a backup of the SOPHOS3 database: backupdb.bat in "\program files\sophos\enterprise console\DB" will do this but I assume you have SQL Server Management Studio installed on the macine also so you could use that.  Either way, as long as you end up with a file such as sophos3.bak

2. Create a new database called SOPHOS3 in the SQL Server 2005 instance.  Ideally choosing separte dedicated physical drive for the data and log files.  

3. Restore the backed up SOPHOS3 database into the new SOPHOS3 database in the SQL 2005 instance.

You can use RestoreDB.bat which can be found in the same localtion as Backupdb.bat, again you could use SQL Server Management Studio.

4. I would then suggest going through the properties of the new SOPHOS3 database and turn off auto shrink and autoclose.  Maybe take a look at: http://www.sophos.com/support/knowledgebase/article/111353.html.

5. Then you need to point the management service at the new instance and database rather than the MSDE one.  To do so:

5.1. Stop the Sophos Management Service.

5.2 Change the connection string that the Sophos Management Service uses.  You'll find it under DatabaseConnectionMS in: HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\EE\Management Tools\.

At the end of the connection string it has:

Data Source=

This should be updated to reflect the machine and the new instance name.

5,3 Also update: HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\EE\Management Tools\Database Installer\Instance to reflect the new instance name, if this is a "no named" instance then enter MSSQLSERVER.  If you don't change this the Sophos Upgrade Advisor will complain that you've moved the database outside of the installer.

5.4 Start the Sophos Management Service and open SEC, everything should be as you left it.

At this point you should still have the 2 instances but now the SEC 3 install is pointing at the SOPHOS3 database in the SQL 2005 instance.  Please ensure it's all working at this stage.  

I would then probably stop the service for the MSDE instance.  Run the Sophos Upgrade Advisor and check that it's happy.  If it complains about moving the database you might need to uninstall the MSDE instace of SOPHOS, I can't remember quite what it checks.  I believe it just reads in both of the above registry keys and checks that they match.  It might check for a SOPHOS instance being installed as well or that MSDE is installed.  If you can leave the MSDE uninstall to after the upgrade to SEC 4 and then SEC 4.5 that would be safer but if it is required to be removed to do the upgrade to SEC 4 then it should be fine.

I hope this helps.

Regards,

Jak