Help Required

  • We have existing three SQL 2012 instances with 140 databases ditributed across all three instances with database mirrioring and SQL clustering setup. Size of all databases on primary is close to 32 TB.

    We have acquired 4 new servers where SQL 2016 installed with AlwaysOn setup in three sql instances. Now we have requirement to move all of above databases which are distributed in three instances to these new instances with minimal downtime. Intially, we thought to break the database mirroring for existing prod DB's and re-setup with new prod but it will work one to one then we started exploring logshipping options which has one to multiple secondaries and this way we would be able to bring all of our databases in new servers with no time during the cutover day and AG setup will be also fast and join only.

    Since, we have lot of databases with 32 TB in size. Do we have any automated logshipping solution which basically help to setup single principal to multiple (four) destinations?

  • I don't have an answer to your question, but please let me point out another issue.

    You're getting ready to hop the 2014 Cardinality Estimation Engine upgrade gap. The new CE was introduced in 2014 and while overall it's either benign or beneficial, in some cases, for queries that were already problematic, you may see degradation in performance. The best approach here, in addition to lots of testing to try to identify the problems early, is to use the Query Store to capture performance metrics of your databases which you keep in the OLD compatibility mode for a period of time. Then, after you've gathered data, switch to the new compatibility mode. Query Store can help you identify any queries that regressed in behavior, and you can use plan forcing as a means of dealing with them short term until you do the longer term fix, which is usually adjusting the query (which again, was nominal in the pre-2014 database).

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply