Connection String Stability

Previous SQL Server Accounts	Connection String Planning Next

It is possible to keep the same Connection Strings to SQL Server that are used by applications or users almost regardless of changes in the underlying SQL Server topography. The problems associated with changing connection string syntax often restrict the scope of topography changes that can be made, which often leads to slow adoption of new versions of SQL Server with a corresponding loss of opportunity to the business when new features cannot be used.

Keeping connection string stability allows all of the following to happen without any impact on how applications or users connect to SQL Server:

• Server names and SQL instance names can change
• Servers can become clustered or unclustered
• Availability Groups can be added or removed
• SQL instances can move between hosted on-premesis or in the cloud

The key to having connection string stability is the use of DNS Aliases. These form an abstraction layer between the application or user and SQL Server, and therefore allow any of the above changes to be made without having to c

The following sections look at how to plan and implement connection string stability:

Item	Description
Connection String Planning	Planning for connection string stability
SQL Server Database Connection Strings	Implementing stable connection strings for SQL Database
Reporting Connection Strings	Implementing stable connection strings for Reporting
Analysis Services Connection Strings	Implementing stable connection strings for Analysis Services
Disaster Recovery Failover Considerations	Maintaining stable connection strings during Disaster Recovery

Copyright FineBuild Team © 2020. License and Acknowledgements

Previous SQL Server Accounts	Top	Connection String Planning Next