3

I have the following scenario:

I created an HA group of two nodes in SQL Server 2016 Standard (which is limited to two nodes, one database per group and a non readable secondary replica). I tried to take a snapshot of the secondary non-readable replica, but it's didn't work and I can do that only on primary replica.

On failover snapshot replication (local publication) is moving automatically on primary replica.

From what I read it's possible to have a snapshot on secondary non-readable replica.

What am I doing wrong?

Improve this question
2
  • Can you give more detail as to what is blocking you from doing this?
    – LowlyDBA - John M
    Commented Oct 7, 2019 at 14:54
  • but it's didn't work - what error do you get ? Snapshot should just work fine.
    – Kin Shah
    Commented Oct 7, 2019 at 15:05

1 Answer 1

Reset to default
1

That link refers to taking a Database Snapshot of the secondary database, which was possible in Database Mirroring.

Remember there are lots of unrelated things that use the word "snapshot" in SQL Server:

Database snapshots are unrelated to snapshot backups, snapshot isolation of transactions, or snapshot replication.

It's not possible to use a Snapshot Replication with a secondary database:

In an availability group a secondary database cannot be a publisher. Republishing is only supported when transactional replication is combined with Always On availability groups.

Replication, change tracking, & change data capture - Always On availability groups

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.