The Last SQL Server Service Pack
SQL Server 2016 SP3, the last service pack ever is out. Steve comments on how the world of software patches has changed.
SQL Server 2016 SP3, the last service pack ever is out. Steve comments on how the world of software patches has changed.
In this article we cover how to implement a batch Databricks Change Data Feed process through an end-to-end exercise.
This video demonstrates a set of queries for estimating data compression savings in SQL Server. It also covers how to make an informed decision on whether data compression makes sense for your data and workload or not.
Steve notes that there are differences between state based development and migration based development, but neither is necessarily better.
In this first level of the SSAS Tabular stairway, learn the benefits of implementing an SSAS solution.
Learn about the various ways to use the GROUP BY command to summarize and rollup query results. We look at the basics with examples as well as using group by rollup, cube and grouping sets.
Join Kevin Davis, DBA Manager at Tower Loan to hear their playbook for successful distributed estate monitoring, and the role of SQL Monitor.
This article looks at moving data in three related tables to Azure SQL Database using the change tracking feature in SQL Server to determine which rows have been changed.
The world of public data is scary for Steve, even when the data is aggregated. It appears that keeping information private is becoming harder, and perhaps, impossible.
Extended Events have been part of SQL Server since 2008. In this article, Ed Pollack explains the building blocks of Extended Events data collection.
Every organization I talk to has the same problem dressed up in different clothes....
By DataOnWheels
I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
Comments posted to this topic are about the item The day-to-day pressures of a...
Hello all, I’m looking for advice on how to derive a daily snapshot table...
We need to replace our Windows server running SQL 2017. Any reason not to...
I have some data in a table that looks like this:
BeerID BeerName brewer beerdescription 1 Becks Interbrew Beck's is a German-style pilsner beer 2 Fat Tire New Belgium Toasty malt, gentle sweetness, flash of fresh hop bitterness. 3 Mac n Jacks Mac & Jack's Brewery This beer erupts with a floral, hoppy taste 4 Alaskan Amber Alaskan Brewing Alaskan Brewing Amber Ale is an "alt" style beer 8 Kirin Kirin Brewing Kirin Ichiban is a Lager-type beerIf I run this, what is returned?
select t1.[key]
from openjson((select t.* FROM Beer AS t for json path)) t1 See possible answers