{"id":1486,"date":"2020-06-25T09:00:23","date_gmt":"2020-06-25T16:00:23","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cosmosdb\/?p=1486"},"modified":"2020-06-25T13:00:22","modified_gmt":"2020-06-25T20:00:22","slug":"powershell-preview","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cosmosdb\/powershell-preview\/","title":{"rendered":"New Azure Cosmos DB PowerShell features for greater enterprise manageability"},"content":{"rendered":"

Enterprise Manageability<\/h2>\n

Azure Cosmos DB enterprise manageability and readiness continues to mature, with multiple management libraries available. The Az.CosmosDB PowerShell package<\/a> lets you directly manage Azure Cosmos DB accounts, databases, containers, throughput, and more across all Azure Cosmos DB APIs. Az.CosmosDB is in public preview with General Availability (GA) expected later this year.<\/p>\n

In my previous post about Az.CosmosDB<\/a>, I introduced it and discussed how to start working with it. In this post, I’ll show some examples for how to work directly with Azure Cosmos DB resources using the PowerShell cmdlets, and I’ll also note several Az.CosmosDB additions to let customers manage new Azure Cosmos DB capabilities including autoscale, analytical storage, free tier, and MongoDB API Server version.<\/p>\n

NOTE<\/strong>: you will need Az.CosmosDB<\/a> 0.1.6 or newer to use the new capabilities discussed below.<\/p>\n

 <\/p>\n

Manage Azure Cosmos DB Resources using Cmdlets<\/h2>\n

The Az.CosmosDB cmdlets enable detailed management of Azure Cosmos DB resources. Below I show you a complete PowerShell script that completes several steps, starting with creation of a new Azure Resource Group with New-AzResourceGroup<\/code>.<\/p>\n

Then I use New-AzCosmosDBAccount<\/code> to deploy a new Azure Cosmos DB account configured for Azure Cosmos DB’s API for MongoDB with compatibility level 3.6 and enabled for analytical store (more on that later in this post). After that, I use New-AzCosmosDBMongoDBDatabase<\/code> to deploy a new database into my new account.<\/p>\n

Next, I use New-AzCosmosDBMongoDBIndex<\/code> to create a new unique index definition with the partition keys. This is one of many cmdlets provided in the Az.CosmosDB package for very granular management of Azure Cosmos DB resources and configurations.<\/p>\n

Last, I use New-AzCosmosDBMongoDBCollection<\/code> to create a new container in the database with the index I created above and configured to enable analytical store and autoscale (more on that later in this post) to a maximum of 4,000 RU\/s.<\/p>\n

https:\/\/gist.github.com\/plzm\/2ec6d0f31089dbbb9eafb64402849e02<\/p>\n

 <\/p>\n

Autoscale<\/h2>\n

Autoscale provisioned throughput is described in this post<\/a> and the Azure Cosmos DB documentation<\/a>. Both databases and containers can be configured with autoscale.<\/p>\n

The Az.CosmosDB cmdlets for database and container management accept a new parameter, -AutoscaleMaxThroughput<\/code>. For example, to configure a container to autoscale instantly up to a maximum of 4,000 RU\/s:<\/p>\n

New-AzCosmosDbSqlContainer [...] -AutoscaleMaxThroughput 4000<\/code><\/p>\n

You can update the configured autoscale max throughput. For example, to increase the autoscale max throughput from 4,000 to 6,000 RU\/s:<\/p>\n

Update-AzCosmosDbSqlContainer [...] -AutoscaleMaxThroughput 6000<\/code><\/p>\n

NOTE<\/strong>: Use either -AutoscaleMaxThroughput<\/code>(for autoscale throughput) or -Throughput<\/code> (for standard throughput) – do not use both together.<\/p>\n

 <\/p>\n

Analytical store<\/h2>\n

Azure Cosmos DB analytical store is a component of Azure Synapse Link, described in this post<\/a> and the Azure Cosmos DB documentation<\/a>.<\/p>\n

To use Azure Cosmos DB analytical store with Azure Synapse Link, first enable analytical store on a new account using New-AzCosmosDBAccount [...] -EnableAnalyticalStorage $true<\/code>, or on an existing account using Update-AzCosmosDBAccount [...] -EnableAnalyticalStorage $true<\/code>.<\/p>\n

Then create new containers with analytical store enabled by using the -AnalyticalStoreTtl<\/code> parameter. Currently, API for MongoDB collections and Cassandra API tables can be enabled for Analytical Store using New-AzCosmosDBMongoDBCollection<\/code> or New-AzCosmosDBCassandraTable<\/code>, and additional Azure Cosmos DB APIs will be supported by GA.<\/p>\n

 <\/p>\n

MongoDB API – Set Server Version<\/h2>\n

New-AzCosmosDBAccount<\/code> now accepts a -ServerVersion<\/code> parameter to specify the MongoDB compatibility level for the new\u00a0 API for MongoDB account. For example: New-AzCosmosDBAccount [...] -ApiKind \"MongoDB\" -ServerVersion \"3.6\"<\/code><\/p>\n

 <\/p>\n

Enable free tier<\/h2>\n

Free tier was introduced on a previous post<\/a>. With free tier, you receive 400 RU\/s throughput and 5 GB storage each month for free for the life of the Azure Cosmos DB account on which it is configured.<\/p>\n

Free tier is available for one Azure Cosmos DB account per Azure subscription and must be configured when the Azure Cosmos DB account is created:<\/p>\n

New-AzCosmosDBAccount [...] -EnableFreeTier $true<\/code><\/p>\n

 <\/p>\n

More Information<\/h2>\n

PowerShell management samples are available for each of the Azure Cosmos DB APIs:<\/p>\n