Tag Info

New answers tagged

1

There really isn't a concept of a connection string in the Availability Group. The AG is based on a Windows Cluster and a Virtual Name in the cluster that is of the type of Availability Group Listener. This listener is configured in Management Studio in the Availability Groups container in Object Explorer. The example that was given above is correct. SQL01 ...


1

The destination path for the LSCopy job has to be an UNC Path for all practical purposes, to make things simpler to debug I would reccomend not to use the default \d$ shares as you will have to change the permissions on them but connecting to \localhost\c$ is a network connection. Now the error ***Error: Not enough server storage is available to process ...


1

If you've set-up an Always On Availability Group Listener (and you should), then you'll have a new virtual name to use in your connection string. So if your SQL Servers are SQL01 and SQL02, and there's an availability group called SQLAG01 - then you'll specify this. You could continue to specify SQL01 in your connection string, but if the Always On ...



Top 50 recent answers are included