on 2018 Apr 13 12:57 PM
I'm wanting to make sure I have my arms wrapped around moving our replication environment from SQLA12 to SQLA17.
We have our production database running on our server. Every hour at the bottom of the hour, we backup the database. We use the following switches...
-r (renames the transaction log ans starts a new log. copies the current working transaction log to our backup directory)
-s (image backup)
A couple other switches are used, but those are the most critical.
The long and the short of it is this. We brought our superintendents into the offices. All systems ran replication. All internal users with replicating databases ran replication. Then we shut down our version 12 database. All outstanding replication is up to date.
Since We're basically going to be doing remote resets on everyone, and then extracting new databases, is there any reason to bring over the transaction log files that were a part of the database? Or should we not worry about that, and instead bring the main db and log file over, and then let replication start over again?
My guess is the reason that our individual log files went back about a year and a half had to do with users that had not possibly replicated that data yet.
So when copying the database over and migrating it from 12 to 17, should I have all the transaction logs with it? Or just the current one?
Hope this question makes sense. If anybody needs clarification, please let me know.
Thanks!
Jeff Gibson
Intercept Solutions
Nashville, TN
User | Count |
---|---|
79 | |
11 | |
10 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.