We have moved!

Thanks for visiting! This blog has now been migrated to: https://techcommunity.microsoft.com/t5/SQL-Server/bg-p/SQLServer/label-name/SQLServerTiger    


We are moving!

This blog is in the process of being migrated to one of the new consolidated SQL Server and Azure SQL Database blogs on the Microsoft TechCommunity website. Once the migration is complete, we will post the new URL along with instructions for how to navigate the new blog and update your RSS feeds. Until then,…

1

Let’s talk about trace flags

One of the most confusing aspects of SQL Server configuration is often trace flags. There are lots of trace flags out there, and while many of them are documented, when to use them and when not to is not always clear. The primary reason for this post is to introduce a new article from Microsoft…

3

Replica Failover within the Secondary Availability Group in a Distributed Availability Group

A distributed availability group (distributed AG) is a special type of availability group that spans two availability groups. This blog will clarify some issues regarding failover in a distributed AG, specifically demonstrates distributed AG resiliency from data loss despite the synchronizing state between the availability groups. A simple distributed AG ‘TIWENDAG’ is created for relevant…

1

SQL Server 2017 on Linux: Support for third-party AD providers

In the past, SQL Server on Linux has required SSSD to be configured for AD Authentication to work. SSSD is a very powerful service which provides support AD authentication and integration. However, there are some third-party AD providers (such as Centrify, PBIS, and VAS) which provide additional value-added services (such as auditing) on top of…


Failover Detection Utility – Availability Group Failover Analysis Made Easy

To analyze the root cause for the failover of an Availability group, users are required to perform coordinated analysis of various logs including the Cluster Logs, SQL Error Logs, and the Availability groups extended events logs. This coordinated analysis of the logs can be difficult and requires extensive knowledge of the internals and the various…

32

String or Binary data would be truncated: replacing the infamous error 8152

In the recent announcement at Ignite 2018 on the release of SQL Server 2019 CTP 2.0, the new Big Data Clusters, data virtualization, support for UTF-8, and Intelligent Query Processing were highlights. But we have also previewed work being done to address the infamous error message “String or binary data would be truncated”. This error…

2

SQL Server 2019 CTP 2.0 New Features – Columnstore support for sp_estimate_data_compression_savings

Next up for new Storage Engine area features in SQL Server 2019 is an update to the sp_estimate_data_compression_savings stored procedure to add support for both columnstore and columnstore archive compression. This stored procedure has been around since SQL Server 2008 and is handy when you are evaluating whether to compress tables and indexes. The procedure…


SQL Server 2019 CTP 2.0 New Features – Introducing the Page Cracker (AKA sys.dm_db_page_info)!

Microsoft Ignite 2018 is fading away in the rearview mirror, but the excitement over all the new features and the vision shared there is just beginning. You’re probably seeing lots of buzz around the new Big Data Clusters, data virtualization and Intelligent Query Processing among others, but I wanted to take some time on the…


SQL Server 2019 Preview

Earlier this week, we announced SQL Server 2019 Public Preview at Microsoft Ignite. All the features that you see in the “What’s New” page are new capabilities that shipped with the CTP 2.0 release. Some of the key changes that people normally wouldn’t associate with SQL Server was the introduction of big data clusters which…