Creating Azure SQL VM with same name as VM
Hi, Currently we have a resource group, which contains a Virtual Machine and SQL Virtual Machine (and a few other resources). The VM and SQL VM has the same name: I want to move this resource group (and its resources) to another subscription. We tried using Resource Mover, but we couldn't as there are backups. I tried the steps in the following link: https://petri.com/copy-azure-vm-using-managed-disk-snapshots/ I was successful in moving 5 of the 6 resources to the new subscription, but was unable to move the SQL virtual machine: I tried to create a SQL virtual machine, but it says I can't create one with the same name: I found that in order to create a VM and SQL VM's with the same name, in the above image, I have to choose an image that has SQL Server and Windows. But this doesn't allow me to use the original managed disk (it only has an OS disk) and it also creates a couple of more disks, which are not in the original resource group. I was wondering if there are recommendations on how to create a SQL VM that has the same name as the VM in the same resource group and are also linked to each other. Jason
How to execute SQL script via Azure Pipeline, please help
How to execute SQL script via Azure Pipeline, please help, I don't want to do it via powershell. Please suggest. For example I will be creating an Azure pipeline.yml where under a stage/job will be having steps to execute an SQL script file(having multiple CRUD operation)Azure SQL Managed Instance - Changing Geo-Replication settings after deployment
Hello Everyone, Do you know if it is possible to change settings of "DNZ Zone" and "DNS Zone Partner" after the deployment of Managed Instance has been completed? https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-failover-group-tutorial According to the documentation there is an option for Geo-Replication settings at the creation. Can I change the settings after creation of Managed Instance so I can create a Failover-Group? Unfortunatlly I did not create the second managed instance myself 😞 Wojtek
