Tag Info

New answers tagged

2

This is how DNS works with multiple servers the client will ask the servers in a round-robin fashion. if an entry is removed from one of the DNS servers the client will get Non-existent domain as an answer from that server and will not query the other. Here you can get an overview but it boils down to this The DNS Client service queries the DNS servers ...


0

Below steps are used if you are using https://ola.hallengren.com/ , SQL Server Maintenance Solution - by Ola hallengren which supports AlwaysON as well. I recommend that you configure it like this: Have the jobs enabled and scheduled on both servers. Add @CopyOnly = 'Y' to the full backup jobs. Drop the differential backup jobs Ola's jobs will then ...


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

First of all grab Ola Hallengren's scripts to do the backups (http://ola.hallengren.com) and drop the maintainance plans. Ola's scripts have much better retention settings and will allow you to set a mark in hours how long to store the backups and know how to take the backups of the secondaries. And for your questions: Set up a small script in SQL Server ...


3

My question is: - Do i have to schedule the jobs at primary replica and then disable them until fail-over occurs and then manually enable jobs or what is the best way to deal with these please? No, you should just add a check with the new function sys.fn_hadr_backup_is_preferred_replica if sys.fn_hadr_backup_is_preferred_replica('your db name') ...


0

Change $SqlServerPrimName = "SERVER\INSTANCE,Port" to $SqlServerPrimName = "SERVER\INSTANCE" and change the port for the instance afterwards. $ComputerName = gc env:computername $SqlServerPrimName = "SERVER\INSTANCE" $SQLServerPort = 1433 $wmi = new-object ("Microsoft.SqlServer.Management.Smo.Wmi.ManagedComputer") $computerName ...


0

For an async replica, perhaps you could (a) create a table with a single row that has a timestamp column that is updated by an job scheduled to run every 10 secs (I don't think agent jobs can be scheduled to run with shorter frequency). This record will then be replicated over to the async replica. Then perform a query against both tables (primary replica ...


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 ...


1

Answering my own question, as future readers will benefit from it : Seems like we might be hitting Longer latency for SQL Server 2012 database when you use Service Broker, database mirroring, and Availability Groups. This is fixed in SQL server 2012 SP2 CU1. The KB 2976982 has a typo(AlawysOn). So if you are searching by AlwaysON, it wont show up. After ...


5

What is the best practice to setup the file share for data synchronization? Network path or local machine You have to really read up on AlwaysON. AlwaysON ships only log blocks. So there is no fileshare concept. On the windows cluster, you can set a witness as fileshare. So, the witness (disk or fileshare) is not AlwaysOn specific. It is required by ...



Top 50 recent answers are included