How to migrate databases from SQL 2012 to SQL 2017 failover cluster using Red Gate tools
We are getting ready to move some interconnected databases (20+) from a single SQL server 2012 standard to a SQL server 2017 enterprise failover cluster(availibility group)
I started testing with backup/restore but this is not very practical for 20+ databases and not very repeatable/scriptable
it also demands that you remove database from availibility group , restore it, re add it to availibility group manual each time
I tried the "copy database wizard" but ran into all sort of issues (timeouts/unable to copy windows logins/...) and databases getting deleted if job fails
We want exact copies so using SQL compare + SQL data compare does not look like the right path
Our databases are not(only partly) under SQL source control
Wich (Red Gate) tools can i use to copy/sync the databases to the new location, without bringing source offline, for testing if everything still works in a clustered environment/new server version?
Wich (Red Gate) tools should i use on day X to do the final migration/sync?
Are there tools for copying and syncing server config to each node:
- linked servers
- notify email operators
- database mail profiles
- SQL logins from windows accounts (+ mappings to databases)
Can you point me to a guide/checklist for this kind of migration