2023-09-06
354 reads
2023-09-06
354 reads
This week Steve found a question of whether SQL Server 2019 uses more CPU than 2016.
2023-04-01
714 reads
2021-09-08
823 reads
In this article, I am going to explain fixing a problem related login failure error with SQL Server. The Problem One of the common error in the SQL Server error log is "Login failed for user 'DomainName\ServerName$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]". Even though it says that […]
2025-12-31 (first published: 2020-11-24)
54,109 reads
Temporal tables were introduced with SQL Server 2016. To take advantage of this feature, you might start fresh with a brand new table. It is possible, however, to convert an existing table with accumulated history to the new functionality. In this article, Mala Mahadevan explains how to create temporal tables for both scenarios.
2019-04-01
In this article, 2nd of 2-part series, we will look at the 3rd approach to import JSON, recap both parts of the series and form a conclusion.
2020-03-20 (first published: 2018-08-27)
6,508 reads
In this article, 1st of 2-part series, we will look at 2 approaches to import JSON in SSIS using 2 methods: the new functionality of SQL Server 2016 and the Json.NET library.
2020-03-13 (first published: 2018-08-20)
32,514 reads
2018-03-13
970 reads
2018-02-15
909 reads
Erik Darling looks at how SQL Server 2016's live query plans react when they're blocked.
2017-11-01
3,227 reads
By Steve Jones
I had an idea for an animated view of a sales tool, and started...
Next Monday, February 9, 2026, my one-day live online training SQL Server Query Tuning...
By Steve Jones
One of the features we advocates have been advocating for is a better way...
Comments posted to this topic are about the item Delta Lake: The Definitive Guide:...
Comments posted to this topic are about the item Databricks Data Intelligence Platform: Unlocking...
Comments posted to this topic are about the item Storytelling with Data: Let's Practice!
In SQL Server 2025, what is returned from this code:
DECLARE @message VARCHAR(50) = 'Hello SQL Server 2025!'; DECLARE @encoded VARCHAR(MAX); SET @encoded = BASE64_ENCODE(CAST(@message AS VARBINARY(1000))); SELECT BASE64_DECODE(@encoded)See possible answers