How to Change collation for production Azure SQL databases
Azure SQL Database only supports changing collation by modifying the model.xml file for .bacpac files. Schedule a maintenance window for your application during the process and stop the workload to prevent loosing updates on your database. Do the export/import to/from databases with a high service tier to boost the operation. Use a VM in the same region to save latency time. If your database is/was used for Data Sync Service, consider removing DSS object before exporting the database. Check: https://techcommunity.microsoft.com/t5/azure-database-support-blog/exporting-a-database-that-is-was-used-as-sql-data-sync-metadata/ba-p/369062 If your database is a part of Geo-DR replication, consider removing the Geo link and delete secondary database before starting the operation in order to create a new Geo replication and sync the new database with the new collation to the secondary server.Lesson Learned #212: Hands-On-Labs:TCP Provider: The semaphore timeout period has expired
We used to have cases where our customer faced the following error message: "TCP Provider: The semaphore timeout period has expired" in this video my colleague Dineu Assis is going to provide us some insights about it.
Lesson Learned #341: Index Disabled vs Performance issues
Today, we got a very interesting service request where our customer reported an issue about performance, where they mentioned that they have an execution plan where in staging environment the filter is using Index Seek and production environment is using Index Scan and they need to know why SQL Server is not using the Index Seek operator when the structure is the same.Lesson Learned #345: How to get the most from Azure SQL Database - Session Delivered
This last April 27 we had a great opportunity and honor to deliver the session how to get the most of your Azure SQL database and Azure SQL Managed Instance with my colleague Sabrin Alsahsah Support Engineer in Azure SQL Database EMEA team.
