Curious if anyone is using a SQL cluster for NTP and if you’ve had any issues. Along the same lines, has anyone had any luck connecting to SQL with a connector string as opposed to ,? Seems for clustering, the connection string is preferred.
1 Like
Hi Art - I know we have several customers using a SQL cluster for the NTP database with no issues. I have asked Alexei to reply with further details.
-Tony
4 Likes
We have tested NTP with SQL Cluster, specifically with the Always On Availability Groups configuration. No known issues at this time.
Also in NTP 7.5 we introduced possibility to add custom parameters to the connection string. For example, now you can specify additional connection string parameters in the EM config file like this:
…add key=“ConnectionStringOptions” value=“MultiSubnetFailover=True”…
1 Like
Outside of 7.5, is there a way to connect to SQL from NTP with anything other than ,? Like a DNS string?
Yes. You can use SQL Server DNS name instead of IP or NetBios name. Just type it during NTP server installation on the step where you configure DB connection.
1 Like
I’ll have to try it again but last time, it did not take the DNS name and it only worked with ,.
Hi Art,
Did this work for you?
We are ready to migrate our database from one SQL box to a new SQL cluster. We’d prefer not to have to uninstall and reinstall NTP, is there a simple way to update the connection string to the new server? We would like to use the MultiSubnetFailover=True as well. However, I don’t see our current SQL setup reflected in the SIEnterpriseManager.exe.config file.
Just noticed that there is a SIDBConfigMgr.exe - would we run that to update the SQL server?
Hi Art - Yes SIDBConfigMgr.exe is used to update the connection string for the NTP main and/or archive DB’s as an alternative to doing an EM uninstall / re-install. Most often used to set a new password if using SQL Auth. It does not move the existing DB files from one server to another. You would have to do that outside of NTP first.
1 Like