No. You can apply transaction logs to a backup. You can't apply them to a live database. You can reduce this window by taking a step-wise approach. If your data essentially moves forward in time, meaning there is a large percentage of the data which will not change during your merge process, you can leave them online and merge that portion of the data which is essentially static at that point in time. This gives you a smaller subset of data to work with on a second pass of merging the data which should reduce the downtime.
Alternatively, you could leverage replication to combine the data together and keep the transactions from the two separate databases synchronized into a third database that you are merging into. Once everything is merged and synchronized, you can cut each plant seamlessly over to the new merged database.
For More Information
- Dozens more answers to tough SQL Server questions from Michael Hotek are available here.
- The Best Microsoft SQL Server Web Links: tips, tutorials, scripts, and more.
- Have a SQL Server tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical SQL Server questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, SQL Server, DB2, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
Dig Deeper on Microsoft SQL Server Installation
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.