I'm planning to do SQL Server migration of SQL Server 2012 to a new hardware and a new version of SQL Server (2016). I'm trying to find the best solution with minimal downtime. I found some suggestions on the internet that in theory sounds great. I'm talking about DB Mirroring and Rolling Upgrade. But I also have read that MS does not recommend DB Mirroring between different SQL Server versions. So now I'm confused should I or shouldn't use DB Mirroring for this. Any suggestions? Have anybody tried that method before? I'm also thinking about Log Shipping.
Sql-server – SQL Server Migration using a DB Mirror (Rolling upgrade)
migrationmirroringsql serversql-server-2012sql-server-2016
Related Question
- Migrating DB, SSIS Packages, SSRS Reports from SQL Server 2008 R2 to 2012
- MySQL Server Migration – How to Migrate MySQL Server to New Hardware
- SQL Server – Upgrade from SQL Server 2012 to 2016
- SQL Server 2008 – Best Approach to Mirror All Databases
- Sql-server – Upgrade/Migration from SQL Server 2008 R2 to SQL Server 2016
- Sql-server – Moving SQL to a hosted server
- Sql-server – SQL Server 2008 R2 upgrade to 2017
- Sql-server – Need to upgrade SQL Server from 2012 to 2017 on a Server 2008 box
Best Answer
We used successfully mirroring to migrate databases from SQL 2005 to SQL 2016 (on new hardware). All worked flawlessly. On hardware that was 13-14 years old and using Windows Server 2003.
Can't say anything about MS support, as since we had such an old version, we didn't have any type of support from MS (not even Extended).
If you're curious, here's a short list of steps we used:
Prerequisites
Mirroring preparation
Actual migration - the only moment of downtime
Everything gets a tad more complicated with replications, but you get the point. It works very well. Log shipping will work too, no worries. But since it involves a bit more manual steps, we preferred to reduce the complexity if possible.