Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 3043 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Multiple Sophos databases on one SQL Server

blardyblar

Hi,

I have a question regarding the Sophos databases.

We have multiple offices configured with their own SEC 5.2.1 and locally installed databases.

To bring this in line with company policies we would like to split and move the databases to fall under dedicated DBA team.

We have successfully split and moved one set of databases (Core, Enc, patch, security) to a SQL server from one of our offices.  However, since we did this as a backup and restore operation the database names have remained as default - sophos521, etc.

Our DBA's would like to host the additional databases (from the additional offices) on the same SQL server, but obviously the databases have the same names.

I've found a bit of detail from the board about Sophos supporting unique instances, but I need to clarify a few points please.  Of course, I'd need to know if the below is supported, or recommended. :smileyhappy:

As I understand it we can change the instance to a unique instance name and if this contains SOPHOS in the name then the installer will detect it.   My knowledge of SQL is limited, but from the layout it looks like our DBA's have the databases assigned to a default instance, along with other databases.   Hopefully, I'm explaining this correctly.

So, for example the DatabaseConnectionMS string in the registry is "...Initial Catalog=SOPHOS521;Data Source=SQLSERVER;"

How would this work if we had multiple databases with Sophos in the name for different offices. 

For example:

SiteASophos521

SiteBSophos521 

Would we be able to point the installer at just one specific "set of databases" for a Site and not "touch" any others?

Also, will Sophos work out the associated databases (Enc, Patch, Security) if they have the same naming pattern?  If we were to maybe manually amend the DatabaseConnectionMS registry key?

Would this be better with a complete custom install instead?  and would this require re-protection of machines?

Sorry for all the information, but I wanted to try and describe clearly what we are trying to accomplish.

Any help and recommendations you can provide is appreciated.


Thanks


Gav

:45657


This thread was automatically locked due to age.
  • 0
    Hello Gav,

    the database NAMES are fixed, the instance is free. You might be able to hack around this but I'd not recommend it (without Platinum Support at least). ;-)
    I'm not a SQL DBA so I have no idea about the cost of an additional instance - but if I'd have to "consolidate and separate" I'd generally (not only in the Sophos case) use separate instances.

    Christian
    :45667
  • 0

    Hi Christian,

    Thanks for your reply.

    That isn't going to work then! :smileywink:

    I've spoken with our DBA's and we can use another SQL server, that is hosted in another site.

    However, I have another question with relation to hosting the database on a remote server because we need to connect through a firewall. 

    Do we just need to open up ports 8192 and 8194 similar to RMS connectivity?

    I've searched around but I can't find a list of ports specific to connecting to a remote database and I figured it was better to add this query onto this post.

    Thanks

    Gav

    :45727
  • 0

    Hello Gav,

    hosting the database on a remote server

    it depends on your SQL configuration (DBAs should be able to answer this). Database connectivity is not related to the Sophos components and their ports (thus 8192/8194 only come into play when the Sophos endpoint software is installed on the SQL server - and then it is for SESC management by SEC like on any other client).

    The following articles should give you an idea: Configuring the Windows Firewall to Allow SQL Server Access (linked from Connecting to SQL Server over the Internet) - as dynamic ports are, well, dynamic it's probably better to configure the instance to use a static port.

    HTH

    Christian

    :45735
  • 0

    Thanks once again Christian.

    I was getting myself confused when the DBA's were asking about specific ports! 

    We have an existing static port configured for other DB traffic.

    Thanks for your help.  I'm happy for you to mark this thread as resolved. :smileyhappy:

    :45737