March 1, 2018 at 9:05 am
I have a publication scenario on SQL Server and I want to keep the data of the subscriber connected to a publisher. If I delete data from the publisher (by removing the triggers that execute the replication) so there is less data in the publisher, the subscriber will always have more data.
Ok, if after this the replication is damaged and I have to generate a new snapshot, will the data that was in the subscriber that I had previously deleted from the publisher be erased? or is it possible to connect them without having to restart the subscriber?
March 1, 2018 at 10:00 am
fmejiavillegas - Thursday, March 1, 2018 9:05 AMI have a publication scenario on SQL Server and I want to keep the data of the subscriber connected to a publisher. If I delete data from the publisher (by removing the triggers that execute the replication) so there is less data in the publisher, the subscriber will always have more data.
Ok, if after this the replication is damaged and I have to generate a new snapshot, will the data that was in the subscriber that I had previously deleted from the publisher be erased? or is it possible to connect them without having to restart the subscriber?
That kind of "change" qualifies in the category of "you need more than just replication". If you're hoping to capture everything that replication captures, and then keep it all forever, then you're going to need a LOT of disk space. Also, you are largely changing the requirement in such a way that replication isn't really the right tool any more. What do you do if someone drops a column on the publisher? If you use replication, it will go away on the subscriber. Replication is designed to keep a 2nd copy in exact sync with the original. It's NOT designed to do what you asked for.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
March 1, 2018 at 11:08 am
sgmunson - Thursday, March 1, 2018 10:00 AMfmejiavillegas - Thursday, March 1, 2018 9:05 AMI have a publication scenario on SQL Server and I want to keep the data of the subscriber connected to a publisher. If I delete data from the publisher (by removing the triggers that execute the replication) so there is less data in the publisher, the subscriber will always have more data.
Ok, if after this the replication is damaged and I have to generate a new snapshot, will the data that was in the subscriber that I had previously deleted from the publisher be erased? or is it possible to connect them without having to restart the subscriber?
That kind of "change" qualifies in the category of "you need more than just replication". If you're hoping to capture everything that replication captures, and then keep it all forever, then you're going to need a LOT of disk space. Also, you are largely changing the requirement in such a way that replication isn't really the right tool any more. What do you do if someone drops a column on the publisher? If you use replication, it will go away on the subscriber. Replication is designed to keep a 2nd copy in exact sync with the original. It's NOT designed to do what you asked for.
Thanks. What is your advice in this case? do you know some tool for something like that?
March 1, 2018 at 11:22 am
Without a lot more detail on EXACTLY what you need to keep, and what kind of transaction volume you are talking about, it would be impossible to offer up anything more than guesswork. I'm not aware of a specific tool that does what you might be looking for, and you may have to code this for yourselves,
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply