I am in the process of setting up server replication using the Central Publisher Model. We are doing this for application availability. The application is a .NET app and this application uses the SQL Server name in the connection string. As far as I know we can’t have two severs on the same domain with the same name. So if our primary server (server A) goes down and that server name is in the connection string how does the application get redirected to our backup server (server B). Thanks for the help.
Server Availability
Hot Topic
- EDB - CeGetDBInformationByHandle
- Making SSAS Developer Edition act like standard edition
- Configuring Database Mail in Sept 05 version
- Question about Aggragation in Measure Group?
- Query cost
- ReportViewer CopyLocalProperty causes an error when set to True
- SQL Native Client Issue
- SQL Server 2005 Sep CTP setup failed.
- Derived Shape - Replacing a column with itself.
- SQL Server 2005 did not install
SQL Server
- Dynamic Excel Sources
- Error in Data-Driven Subscription
- Connect SQL Server Express 2005 on a remote Computer
- Deny an Application?
- how to get Alias name in columns and mapped column from views
- Error rsFailedToDecryptConfigInformation
- Login failed for user '<<domain>>\<<server>>$'.
- What interface does Management Studio use?
- DMX Query
- How reliable is Microsoft's type4-JDBC driver for MsSQL Server????
Server Availability
Dante Shamest
It should be the application's responsiblity to perform the switch from ServerA to ServerB when it detects ServerA is down. You may need some logic in your application to do so if you want all this happen automatically without user intervention. Or in the case the application can not be modified (if it's a 3rd party software), one thing you can do is to create a SQL Server alias on your application machine pointing to ServerA initially, when ServerA is down, then manually modify the SQL alias pointing to ServerB (keep the same alias name though so no need to modify the application), your application may need to be restarted depends on how it's written.
If your sole purpose to use replication is for application high-availablity, you may also consider DB-Mirroring feature which will be fully available in SQL Server 2005 SP1.
You can also investigate if there is 3rd party software can achieve your goal.
Hope that helps!
Zhiqiang Feng
This posting is provided "AS IS" with no warranties, and confers no rights.