Brilliant and helpful streaming regarding the migration from on prem to DbaaS, thanks indeed!!
@silusvilus6544 Жыл бұрын
Thank you so much for this. Currently working on a migration project and this is helpful.
@timromano7085 Жыл бұрын
@4:25 "You can deploy your database to managed instance and not really have to make any code changes to your application. That's not strictly true. Like any cloud service, cloud services fail-over on you...and your application might lose connection. So it's important that you have retry intervals and things like that". Depending on the complexity of the application, retrofitting "things like that" can become quite an undertaking!
@armando39653 жыл бұрын
Man... you are awesome!
@kishore2vinee3 жыл бұрын
Hi Ellis, Thank you for your valuable information. I have few questions. 1. How can we migrate to MI in which on-prem sql DB has linked servers with oracle, teradata and postgress, any work around for the above linked servers. 2. DMA report has one unsupported feature (PowerShell job step is not supported) 3. Work abound for SSIS jobs 4. Look into if there is any solution for being able to reboot of server within the Managed Instance 5. Look into any technologies that can duplicate Microsoft ACE in Managed Instance
@Ike_Ellis3 жыл бұрын
1. You would need to use SQL in a VM for linked servers like that.
@Ike_Ellis3 жыл бұрын
2. Not sure what the question is here.
@Ike_Ellis3 жыл бұрын
3. Good document on SSIS migration to Azure SQL DB MI: docs.microsoft.com/en-us/azure/dms/how-to-migrate-ssis-packages-managed-instance
@Ike_Ellis3 жыл бұрын
4. You will not be able to reboot an MI. That is not on any roadmap Microsoft has publicly talked about.