2023-09-06
354 reads
SQL Server 2016
Has SQL Server Performance Improved?
This week Steve found a question of whether SQL Server 2019 uses more CPU than 2016.
2023-04-01
711 reads
2021-09-08
821 reads
Fixing "Login failed for user" error in SQL Server
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-11-25 (first published: 2020-11-24)
51,465 reads
Converting a History Table into a System-Versioned Temporal Table
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
Approaches to Import JSON in SSIS (SQL Server 2016+) Part 2
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,456 reads
Approaches to Import JSON in SSIS (SQL Server 2016+) Part 1
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,448 reads
2018-03-13
969 reads
2018-02-15
908 reads
Live Query Plans and Blocking
Erik Darling looks at how SQL Server 2016's live query plans react when they're blocked.
2017-11-01
3,227 reads
Blogs
Why Optimize CPU for RDS SQL Server is a game changer
One feature that I have been waiting for years! The new announcement around optimize...
Performance tuning KubeVirt for SQL Server
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
T-SQL Tuesday #193 – A Note to Your Past, and a Warning from Your Future
By DesertDBA
I haven’t posted in a while (well, not here at least since I’ve been...
Forums
i noticed the sqlhealth extende event is on by default , so can i reduce
hi, i noticed the sqlhealth extended event is on by default , and it...
New-AzSqlInstanceServerTrustCertificate - Failed and no clues
Using New-AzSqlInstanceServerTrustCertificate to import a certificate and get the message New-AzSqlInstanceServerTrustCertificate: Long running operation...
Refactoring SQL Code
Comments posted to this topic are about the item Refactoring SQL Code, which is...
Question of the Day
The Read Committed Snapshot Isolation behaviour
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers