Microsoft Data Migration
Home
Options
1,633
Jim Toland on 04-11-2019 08:26 PM
525
Jim Toland on 04-02-2019 07:49 PM
1,307
Jim Toland on 03-20-2019 10:12 AM
701
Jim Toland on 03-18-2019 06:03 PM
1,031
Jim Toland on 03-16-2019 04:09 PM
865
Jim Toland on 03-16-2019 03:13 PM
878
Jim Toland on 03-13-2019 05:20 PM
516
Jim Toland on 03-13-2019 05:18 PM
542
Jim Toland on 03-13-2019 05:18 PM
445
Jim Toland on 03-13-2019 05:17 PM
392
Jim Toland on 03-13-2019 05:15 PM
519
Jim Toland on 03-13-2019 05:15 PM
560
Jim Toland on 03-13-2019 05:15 PM
194
Jim Toland on 03-13-2019 05:14 PM
255
Jim Toland on 03-13-2019 05:14 PM
163
Jim Toland on 03-13-2019 05:14 PM
206
Jim Toland on 03-13-2019 05:14 PM
240
Jim Toland on 03-13-2019 05:14 PM
179
Jim Toland on 03-13-2019 05:12 PM
173
Jim Toland on 03-13-2019 05:12 PM
197
Jim Toland on 03-13-2019 05:12 PM
168
Jim Toland on 03-13-2019 05:12 PM
251
Jim Toland on 03-13-2019 05:12 PM
167
Jim Toland on 03-13-2019 05:12 PM
178
Jim Toland on 03-13-2019 05:12 PM
268
Jim Toland on 03-13-2019 05:12 PM
188
Jim Toland on 03-13-2019 05:11 PM
340
Jim Toland on 03-13-2019 05:11 PM
204
Jim Toland on 03-13-2019 05:11 PM
267
Jim Toland on 03-13-2019 05:11 PM
Latest Comments
@yogesh1985, migrations to SQL VM are currently supported only by using the Azure DMS UI experience.
0 Likes
This solution was designed and implemented well before Managed Instance was available (2+ years ago). Today, we would likely use MI for the publishing tier. The customer is also exploring using MI instead of Azure SQL DB, which allows them to provide their customers multiple independant data sources...
1 Likes
I'm in the processes of finalizing a solution like this, this doc helps me support my case, just wish that it had emphasized manage sql for the 1st layer:).
1 Likes
@tony roth, yes, you can replace the IaaS SQL layer with managed SQL.
0 Likes
Could the iaas sql layer be replaced with managed sql?
0 Likes