About Us

Latest tech world updates and news form all around the world at Mexicom.org


Configuring Azure SQL Databases Using Azure Resource Manager Templates


In the latest article (Using Azure Resource Manager Templates To Provision Azure SQL Databases) posted on this website, a sample Azure Resource Manager template was changed into a supplied one that provides a new logical server website hosting an unmarried Azure SQL Database example. Template-based provisioning simplifies deployment and promotes DevOps and Infrastructure as Code standards, making it the recommended approach for implementing cloud-based total services. However, its advantages extend past initial implementation because you can use it to configure and keep existing Azure SQL Database times. In this text, you are supplied with an example of this approach.

When considering the use of ARM templates for editing the configuration to existing instances of an Azure SQL Database, it is essential to observe that template deployments are incremental by using the default. As a result, the scope of changes is limited to resources and residences explicitly referenced inside the template. In contrast, all others within the equal useful resource institution remain intact. This simplifies template authoring and minimizes the length of template deployment. Consider a scenario in which Azure SQL Database auditing wishes to be enabled on a logical server (which, using a default, is inherited through all its databases). This configuration is managed with the aid of the properties of the auditing settings resource kind:


As you may see, the configuration calls for admission to a present Azure Storage account, which is set up based on the mixture of the account name and one of its keys. The auditing settings also require a present Azure SQL Database logical server. To put in force the useful resource, a template is used to automatically provision the storage account so that its handiest parameter can be the logical server call. There are a few extra interesting factors of the template:

The name of the storage account should be globally particular. To generate it, rely upon the unique string() function with the seed fee derived from the aid institution identifier (assumed globally unique). The ensuing string can also be prepended with the ‘st’ prefix using the concat() function to ensure that making a rage account call starts with a letter. The garage account name is stored in a variable to facilitate multiple references to its value during the template. The value of the primary storage account key is retrieved using the list-keys() feature. The target Azure vicinity in which the deployment takes region is determined based totally on the vicinity of the resource organization. Note that this presumes that the aid institution’s vicinity matches the area of the logical server.

Geneva A. Crawford
Twitter nerd. Coffee junkie. Prone to fits of apathy. Professional beer geek. Spent several years buying and selling magma in Miami, FL. Spent a year lecturing about psoriasis in Las Vegas, NV. Managed a small team writing about circus clowns in Las Vegas, NV. Garnered an industry award while writing about lint in the financial sector. Spoke at an international conference about getting my feet wet with dust in Libya. Spoke at an international conference about researching rocking horses in Bethesda, MD.