In a scenario where a transactional replication is configured (with no updateable subscriptions) and not for replication is used for every constraints (triggers, check constraints, foreign keys, identity)
If on the publisher I have the following transaction:
Insert Table 1 VALUES (x,y,z, etc.)
Insert Table 2 VALUES (x,y,z, etc.)
Will the transaction still be atomic all the way up to the subscriber side? Even with a crash whatever where it occurs (publisher, distributor, network, subscriber etc)
Either Table 1 and Table 2 is there at the same time or none of them (just like a normal transaction atomicity) on the subscriber?