Lesson Learned #438:Sync failed with state: SyncSucceededWithWarnings, Syncgroup: XXX
Working on a service request our customer reported the following error message: Sync failed with state: SyncSucceededWithWarnings, Syncgroup: XXX - Error #1: SqlException ID: XXXX-NNN-ZZZZ-YYYY-FFFFFFFF, Error Code: -2146232060 - SqlError Number:547, Message: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Table1". The conflict occurred in database "DB1", table "dbo.Table1", column 'Id'. SqlError Number:3621, Message: SQL error with code 3621Lesson Learned #63: It is possible to create Linked Server in Azure SQL Managed Instance?
First published on MSDN on Jan 19, 2019 The answer is Yes!!! and to create it you only need to follow up the instructions provided in this URL Unfortunately, nowadays, you only are able to use the SQL provider to connect to Azure SQL Database, SQL Server or Azure SQL Managed Instance.Lesson Learned #433:Azure SQL Pre-login Handshake Error 64:"The specified network name is no longer"
Encountering error code 64 while connecting to an Azure SQL Database can be a frustrating experience for both DBAs and developers. The error often looks like this: A Connection was sucessfully establish with the server, but then an error occurred during the pre-login handshake (Provider: TCP Provider, Error:0 - The specified network name is no longer available) (Micorosoft SQL Server, Error: 64) - This article aims to clarify the potential causes of this specific error message and offers targeted solutions. Special attention is given to transitions from public to private endpoints within Azure SQL Database, which may trigger this issue.Stop Azure SQL Database
We have several cases where our customers are looking for ways to stop an Azure SQL Database. Some common scenarios where our customers request this option are when they want to decommission an Azure SQL Database and want to ensure that no one is using the database, or because the customer wants to save some money and stop the database during the hours they are not using it. Stopping an Azure SQL Database is not currently supported, but there are several options that could be helpful in these scenarios:Invoke-Sqlcmd with Azure Automation for Azure SQL database
In this blog article, we will be illustrating the required steps to use Invoke-Sqlcmd against an Azure SQL database from Azure Automation. We have received a few cases where customers would like to automate a specific script to be executed on their Azure SQL database like select, update, insert or delete.
