• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 251
  • Last Modified:

SQL Transactional Replication

i just set up transactional replication yesterday. I have 2 servers(Server A and Server B) Server A is my production server and has the publication database on it. Server B is my reporting server and has both the subscription and the distribution databases.  The publication database on Server A gets restored every night from a backup. All day everything ran smooth. Then when publication database got restored I noticed the snapshot agent stopped. How do I keep this from happening? How do I get it started again? keep in mind my topology when answering. Thanks!
1 Solution
Then its better you don't create a replication. Just restore the same database to server B along with Server A every night.
cheryl9063Author Commented:
I have to. They want real time reporting up to 5 minutes. This database is 1.5TB in size and simply restoring will not work. So right now I'm only practicing. The real publication database will never get restored unless something bad happens. But what if it does? Based on the topolgy I chose would there be a potential problem?
In such case, you need to stop replication while your publication DB is being restored and once restore is done, you need re-snapshot to subscriber on Server B and restart the replication for rest of the day.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now