Assume that you install azdata to manage Microsoft SQL Server Big Data Clusters (BDC). When you upgrade SQL Server 2019 BDC fromthe SQL Server 2019 Servicing Update (GDR1) to a SQL Server 2019 CumulativeUpdate (CU), you notice that the additional cluster resources are removed when you use the "azdata bdc delete" command.
For example, when you run the following commands, you notice that the "azdata bdc delete –name BdcOne" command triggers a controller deletion on BdcOne under K8sOne. This may remove these older resources but not the new resources that are located under K8sTwo.
- azdata bdc create –name BdcOne # in K8sOne
- azdata login –name BdcOne # in K8sOne
- azdata bdc create –name BdcOne # in K8sTwo
- azdata bdc delete –name BdcOne # unintentionally removes resources under K8sOne
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following content:
Windows .msi download: https://download.microsoft.com/download/f/f/f/fffaa914-d4f7-4885-89c7-696bbfe7670a/azdata-cli-15.0.2070.41.msi
Linux native package by using "apt" (version 15.0.2070.41): Install azdata to manage SQL Server Big Data Clusters onLinux