Behind the Scenes on OPTIMIZE_FOR_SEQUENTIAL_KEY
In SQL Server 2019 CTP 3.1 a new index option was added called OPTIMIZE_FOR_SEQUENTIAL_KEY that is intended to address a common issue known as last page insert contention. This articles takes a closer look at how the technology behind this new option works and the problem it attempts to address.Adaptive Index Defrag
First published on MSDN on Jul 03, 2011 Latest update: 1/20/2017 (Check change log)Download on GitHubNOTE: if using SQL Server 2012 or SQL Server 2014, mind there is a bug where the online index rebuild can cause index corruption or data loss when it is used together with concurrent queries that modify many rows.Troubleshooting High HADR_SYNC_COMMIT wait type with Always On Availability Groups
First published on MSDN on Apr 12, 2017 HADR_SYNC_COMMIT indicates the time between when a transaction ready to commit in the primary replica, and all secondary synchronous-commit replicas have acknowledged the hardening of the transaction commit LSN in an AG.Update- Beta program for SQL Server on Windows container is suspended.
As you may be aware, the SQL Server on Windows Containers Beta program began in 2017. It has remained in Beta mode meant for only test and development environment until now. Due to the existing ecosystem challenges and usage patterns we have decided to suspend the SQL Server on Windows Containers beta program for foreseeable future. Should the circumstances change, we will revisit the decision at appropriate time and make relevant announcement. Hence with immediate effect, the docker hub repos "microsoft/mssql-server-windows-express" and "microsoft/mssql-server-windows-developer" and the tags within these repos will be deleted and images from these repos will not be available for download going forward. We look forward to your continued support and feedback to help us improve. SQL Server on Linux containers continue to be supported for production environment. This announcement only affects SQL Server on Windows container that was in Beta mode until now. Thanks, Amit Khandelwal Senior Program Manager
SQL Server 2016/2017: Availability group secondary replica redo model and performance
First published on MSDN on Jun 01, 2018 When availability group was initially released with SQL Server 2012, the transaction log redo was handled by a single redo thread for each database in an AG secondary replica.
