You can find the archive for this show here.
Rick Weyenberg email: email@example.com twitter: @codeboarder
Mark Garner email: firstname.lastname@example.org twitter: @mgarner
Google Play: aka.ms/afn-google
Performance best practices for using Azure Database for PostgreSQL – Connection Pooling
- This blog is a continuation of a series of blog posts to share best practices for improving performance and scale when using Azure Database for PostgreSQL service. In this post, we will focus on the benefits of using connection pooling and share our recommendations to improve connection resiliency, performance, and scalability of applications running on Azure Database for PostgreSQL.
Simplify Always On availability group deployments on Azure VM with SQL VM CLI
- Always On availability groups (AG) provide high availability and disaster recovery capabilities to your SQL Server database, whether on-premises, in the cloud, or a combination of both. Manually deploying an availability group for SQL Server on Azure Virtual Machines (VM) is a complex process that requires understanding of Azure’s infrastructure, but new enhancements have greatly simplified the process.￼￼We recently published a new method to automate Always On AG deployments on Azure VM with SQL Virtual Machine Resource Provider via Azure quickstart templates. Today, we are proud to share that we have further simplified this automation with Azure SQL VM CLI, the management API for SQL VM resource provider.
￼Analytics in Azure is up to 14x faster and costs 94% less than other cloud providers. Why go anywhere else?
- In the most recent study by GigaOm, they found that Azure SQL Data Warehouse is now outperforming the competition up to a whopping 14x times. No one else has produced independent, industry-accepted benchmarks like these. Not AWS Redshift or Google BigQuery. And the best part? Azure is up to 94 percent cheaper.
Reserved instances now applicable to classic VMs, cloud services, and Dev/Test subscriptions
- Features that we are launching today:￼1. Classic VMs and Cloud Services users can now benefit from the RI discounts￼RIs with the instance size flexibility option enabled will now apply the discount to both classic VMs and cloud services. For cloud services, the reservation discount applies only to the compute cost. When the reservation discount is applied to cloud services, the usage charges will be split into compute charges (Linux meter) and a cloud services charges (cloud services management meter). Learn how the reservation discount applies to Cloud Services.￼￼2. Enterprise Dev/Test and Pay-As-You-Go Dev/Test subscriptions can now benefit from the RI discounts￼Newly purchased RIs or existing RIs can now be applied to your Dev/Test subscriptions. VM usage on Dev/Test subscriptions will be automatically eligible for the RI discount and all existing reservations with shared scope will be updated to apply discounts to Dev/Test subscriptions.
Account failover now in public preview for Azure Storage
- Today we are excited to share the preview for account failover for customers with geo-redundant storage (GRS) enabled storage accounts. Customers using GRS or RA-GRS accounts can take advantage of this functionality to control when to failover from the primary region to the secondary region for their storage accounts.￼￼Customers have told us that they wish to control storage account failover so they can determine when storage account write access is required and the secondary replication state is understood. ￼￼If the primary region for your geo-redundant storage account becomes unavailable for an extended period of time, you can force an account failover. When you perform a failover, all data in the storage account is failed over to the secondary region, and the secondary region becomes the new primary region. The DNS records for all storage service endpoints – blob, Azure Data Lake Storage Gen2, file, queue, and table – are updated to point to the new primary region. Once the failover is complete, clients can automatically begin writing data to the storage account using the service endpoints in the new primary region, without any code changes.
Source: Azure Flash News
Source Link: Azure Flash News Episode for 2019-02-08