Tag Info

New answers tagged

1

The first attempt would be to try to get either the primary replica back online, or to get the synchronized secondary replica online to ensure that there is no data loss. But provided this is a true disaster recovery scenario (as your original question implies), then it would seem as though your actual cluster (WSFC) has failed. With the database entering ...


1

An alternative you haven't considered is DNS. Obviously changing the connection string is easiest, but if that is a problem for some reason, you could leave the connection strings alone and remap using DNS. More importantly, think about these questions: Why do you need to rename the server/cluster? Is the rename essential to business processes, or is it ...


0

This error was resolved by adding a second IP to the listener. The IP address for both subnets cannot be an IP address already in use, i.e. the IP address of one of the nodes. A DNS entry is also not needed since the Listener creates the DNS entry as part of the process.


0

I am talking about database mirroring as I am not sure whether this discussion holds same for AG which I assume it will be. I am talking about Synchronous mirroring and as per my knowledge actually following happens Following happens when suppose DML is started on Database principal 1.The transaction Log record from DML transaction would be inserted into ...


1

Create a new table Table_A_Archive with exactly the same schema as Table_A_Changes. Partition both these tables by, say, one-month date ranges. As data becomes stale in Table_A_Changes swap that partition out and swap it into Table_A_Archive. Your data retention policy can be efficiently enforced this way, too. A view which unions the two tables can make ...



Top 50 recent answers are included