I have two instances of SQL server running on two different machines:
One is a publisher, the other is a subscriber for a single (large) database. The replication type is transactional.
They both start off with the same snapshot of my replicated database.
I have a utility which runs on the publisher machine which executes the SQL commands against it (all are inserts, updates, deletes). These changes are then pushed out to the subscriber.
I want to know if I am able to TRUNCATE the data in the publisher database so that it has a lower overhead (all I want is the replication ability, I couldn't care less about the actual data in my replication publisher as long as it makes it to the subscribers).
If I do the above and also modify my utility which executes commands to turn INSERTS and UPDATES into a MERGE command, will the data be properly replicated to all subscribers?
The original command that my utility will execute:
UPDATE calendar SET active = 0 WHERE id = 1932
The publisher database doesn't have a calendar record with id of 1932, because I truncated it, so an update will affect zero records.
But the subscriber database DOES have a calendar record with id 1932.
If my utility translates the UPDATE above into a MERGE, will the change be pushed out to the subscriber database even though it executes as an INSERT on the publisher, but an UPDATE on the subscriber?
Thanks in advance.