Enterprise Console 4.5.1 install on Windows Server 2008 R2

Hi,

You can manually create a SOPHOS45 database in the instance using installDB.bat from the DB directory however......

I would strongly suggest creating a dedicated Sophos instance using SQL Express 2008.  I think it is less likely to cause you issues later on.  Two applications sharing SQL Express instances that don't have regard for the other application could be a problem. E.g. one of the applications may in the future no longer supports that version of SQL and needs to be upgraded, the other application may not be supported with that new version.  Then you're stuck installing another instance, moving databases, reconfiguring software to point to the new location, etc..   Is MICROSOFT##SSEE a SQL Express 2005 Embedded Edition?  If so I don't think Sophos strictly support that version of SQL Express, that's not to say it won't work, it just better to stay within the tested scenarios at least when there is a choice.

Two or more SQL express instances is not uncommon on a machine will not cause a resource problem. The additional resource is not so much the additional SQL process to host the database and the file set but more the database itself and the memory and disk I/O that goes along with it.  You'll still have that regardless of where the databases reside.  To help with performance, I would suggest having the MDF and LDF on dedicated drives as this will help speed up I/O and maybe add additional RAM if needed.

I can see the benefit of using a dedicated SQL server install on dedicated hardware, e.g. a cluster, which is more the norm in enterprise environments, but this typically is mainline 2005/2008 to host multiple databases and these versions are more respected and planned for by software vendors such as Sophos.

Thanks,
Jak

Hi,

You can manually create a SOPHOS45 database in the instance using installDB.bat from the DB directory however......

I would strongly suggest creating a dedicated Sophos instance using SQL Express 2008.  I think it is less likely to cause you issues later on.  Two applications sharing SQL Express instances that don't have regard for the other application could be a problem. E.g. one of the applications may in the future no longer supports that version of SQL and needs to be upgraded, the other application may not be supported with that new version.  Then you're stuck installing another instance, moving databases, reconfiguring software to point to the new location, etc..   Is MICROSOFT##SSEE a SQL Express 2005 Embedded Edition?  If so I don't think Sophos strictly support that version of SQL Express, that's not to say it won't work, it just better to stay within the tested scenarios at least when there is a choice.

Two or more SQL express instances is not uncommon on a machine will not cause a resource problem. The additional resource is not so much the additional SQL process to host the database and the file set but more the database itself and the memory and disk I/O that goes along with it.  You'll still have that regardless of where the databases reside.  To help with performance, I would suggest having the MDF and LDF on dedicated drives as this will help speed up I/O and maybe add additional RAM if needed.

I can see the benefit of using a dedicated SQL server install on dedicated hardware, e.g. a cluster, which is more the norm in enterprise environments, but this typically is mainline 2005/2008 to host multiple databases and these versions are more respected and planned for by software vendors such as Sophos.

Thanks,
Jak