December 3, 2024 at 7:40 pm
I've set up replication in my SQL 2019 environment in attempt to migrate SQL databases individually from one datacenter to another. in my testing of one database several issues were found and any advice would be appreciated.
1. There several missing indexes
2. very large tables cannot be filtered on for transaction replication(post snapshot migration)
3. it takes 1-2 minutes for the transaction to publish (even if there were no database changes) but the subscriber takes the publication near instantly.
4. every publication generates a large data file that's the same size regardless of any data changes.
December 4, 2024 at 6:40 pm
Hard to know what you're doing here, as we can't see config. In general, I wouldn't use replication here.
I'd backup and restore. Once you have a full starting to restore, start to create diffs on the source. Once the full is restored, move a diff and restore that. Start to add log backups on the primary, at shorter intervals and restore those on the secondary.
At some point you should have log backups down to a short period of time. Then quiesce the system and move the final log over, restore, run recovery.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply