Failure during copy from blob to sql db using ADF
Hello, I get this error when using Azure Data Factory for copying from blob to azure SQL DB:- Database operation failed. Error message from database execution : ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.. I am able to connect to my DB using SSMS and I have enabled firewall to connect to Azure services. Has anyone faced this error when using ADF / know how to fix it? Thanks in advance.Azure SQL Database now offers zone redundant Premium databases and elastic pools
Azure SQL Database Premium tier supports multiple redundant replicas for each database that are automatically provisioned in the same datacenter within a region. This design leverages the SQL Server AlwaysON technology and provides resilience to server failures with 99.99% availability SLA and RPO=0. With the introduction of Azure Availability Zones, we are happy to announce that the SQL Database now offers built-in support of the Availability Zones in its Premium service tier. By placing the individual database replicas to different availability zones, it makes the Premium databases resilient to the much larger set of failures, including catastrophic datacenter outages. The built-in support of Availability Zones further enhances the High Availability (HA) solutions in Azure SQL Database. For more information see High-availability and Azure SQL Database. To take advantage of this capability, you simply select the zone redundant option during the database or elastic pool creation. You can also enable it for existing databases or pools. If the availability zones are supported in the region where your database or pool is deployed, Azure SQL will automatically reconfigure it without any downtime. Read more about it in the Azure blog.
SSIS Problem Downloading from Azure Blob
Hi All, I'm thrilled to be working on an SSIS project that will (hopefully) get deployed to Data Factory. While getting my SSIS job setup, I added a step to download files from Azure Blob Storage. After adding a Azure Blob Download task, in the control flow, and entering in the storage configuration (test worked successfully), I get the following errors: SSIS package "C:\....\Package.dtsx" starting. Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning. Error: 0xC001000E at Package: The connection "{27A6966C-8398-4C75-84C3-6007B96EEED4}" is not found. This error is thrown by Connections collection when the specific connection element is not found. Error: 0xC001000E at Package: The connection "{27A6966C-8398-4C75-84C3-6007B96EEED4}" is not found. This error is thrown by Connections collection when the specific connection element is not found. Error: 0xC001000E at Package: The connection "{27A6966C-8398-4C75-84C3-6007B96EEED4}" is not found. This error is thrown by Connections collection when the specific connection element is not found. Error: 0xC0024102 at Azure Blob Download Task: The Validate method on the task failed, and returned error code 0x80131500 (The connection "{27A6966C-8398-4C75-84C3-6007B96EEED4}" is not found. This error is thrown by Connections collection when the specific connection element is not found. ). The Validate method must succeed and indicate the result using an "out" parameter. Error: 0xC0024107 at Azure Blob Download Task: There were errors during task validation. Warning: 0x80019002 at Package: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (10) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. SSIS package "C:\....Package.dtsx" finished: Failure. The program '[18968] DtsDebugHost.exe: DTS' has exited with code 0 (0x0). I have confirmed that the GUID here is indeed pointing to the Azure Blob Connection. I'm not sure how to fix, or to get more information on the problem. For what it's worth, this error pops up very soon after launching in Debug mode - only some pre-validation runs (successfully) prior to this error. Any help is appreciated. Thanks!Data Integrity in Azure SQL Database
Microsoft takes data integrity very seriously. While there are some traditional techniques used by DBAs in SQL Server to monitor data integrity (e.g. DBCC CHECKDB) and various methods to recover from database corruptions, the Azure SQL Database engineering team has been able to develop new techniques that can handle some classes of corruption automatically and without data loss. These techniques are used as part of the service to avoid data loss and downtime in the cases where they can be avoided. This blog post outlines some of those techniques, how they work, and what impact it has on customers concerned with what steps they should take to safeguard their data in Azure SQL Database. Read about it in the Azure blog.New multi-tenant patterns for building SaaS applications on SQL Database
We’re delighted to announce the availability of an expanded set of sample SaaS applications, each using a different database tenancy model on SQL Database. Each sample includes a series of management scripts and tutorials to help you jump start your own SaaS app project. These samples demonstrate a range of SaaS-focused designs and management patterns that can accelerate SaaS application development on SQL Database. This is an expansion of the sample Wingtip SaaS application launched earlier this year. Read about it in the Azure blog.
Using SqlPackage.exe in Azure App Service
We are planning to use SqlPackage.exe to do some export / import bacpac of Azure SQL Server databases from a web application hosted also under azure as an app service. But to do so, we need to copy the exe file will all the dlls located under "C:\Program Files (x86)\Microsoft SQL Server\130\DAC\bin\" is it allowed to copy the SqlPackage.exe with all its dependencies and deploy it to Azure App Service?How to configure Azure SQL Database Geo-DR with Azure Key Vault
Azure SQL Database and Data Warehouse offer encryption-at-rest by providing Transparent Data Encryption (TDE) for all data written to disk, including databases, log files and backups. This protects data in case of unauthorized access to hardware. TDE provides a TDE Protector that is used to encrypt the Database Encryption Key (DEK), which in turn is used to encrypt the data. With the TDE and Bring Your Own Key (BYOK) offering currently in preview, customers can take control of the TDE Protector in Azure Key Vault. Taking advantage of TDE with BYOK for databases that are geo-replicated to maintain high availability requires to configure and test the scenario carefully. Read more about it in the Azure blog.Transparent Data Encryption with customer managed keys in Azure SQL Database generally available
Today, we are excited to announce the general availability of Transparent Data Encryption (TDE) with Bring Your Own Key (BYOK) support for Azure SQL Database and Azure SQL Data Warehouse. This is one of the most frequently requested features by enterprise customers looking to protect sensitive data and meet regulatory or compliance obligations that require implementation of specific key management controls. TDE with BYOK support is offered in addition to TDE with service managed keys, which is enabled by default on all new Azure SQL Databases. TDE with BYOK support uses Azure Key Vault, which provides highly available and scalable secure storage for RSA cryptographic keys backed by FIPS 140-2 Level 2 validated Hardware Security Modules (HSMs). Key Vault streamlines the key management process and enables customers to maintain full control of encryption keys and allows them to manage and audit key access. Read about it in the Azure blog.
