Azure DevOps Pipeline with Public Managed Instance

dawid_karszniewicz

Hi!

Currently the ReadyRoll Deploy Database Package stage in the Azure DevOps pipelines is appending the .database.windows.net to the AzureTargetServer property during deployment.

However, there is an issue arising where if I have a public endpoint, this does not work as the port is specified after the connection string. For example, sqlmanaged.public.dnszone.database.windows.net,3342 as the AzureTargetServer is then sent through the task as sqlmanaged.public.dnszone.database.windows.net,3342.database.windows.net, which understandably errors out.

These are the following configurations I've tried:

• sqlmanaged.public.dnszone
• sqlmanaged.public.dnszone,3342
• sqlmanaged.public.dnszone.database.windows.net
• sqlmanaged.public.dnszone.database.windows.net,3342
• tcp:sqlmanaged.public.dnszone
• tcp:sqlmanaged.public.dnszone,3342
• tcp:sqlmanaged.public.dnszone.database.windows.net
• tcp:sqlmanaged.public.dnszone.database.windows.net,3342

Each of which has errored out. Is there a solution for using a public managed instance and specifying the port in the YAML task?

Kind regards,

Dawid.

Eddie D

Hi Dawid, thank you for your forum post.

The only advice or help document I can find is available here.

However, ReadyRoll and the document I refer above has been deprecated.  Ideally you need using the SQL Change Automation  and the Azure DevOps addons, further reading available here. Plus information on a YAML pipeline here.

Many Thanks
Eddie