Preferred Node Policy-Setting on Traditional SQL Cluster
Preferred node setting facilitates instances on traditional cluster to be on the correct nodes which will lead to load-balancing of the resources.
2017-02-02
4,066 reads
Articles
Seven Monitoring Scripts
Joe has a bunch of small, easy to use scripts that can definitely be the beginning of a great set of monitoring tool. Amazing how much info you can gather with a little bit of code!
2017-02-02 (first published: 2003-06-13)
53,764 reads
SQL Server Execution Plans, Second Edition by Grant Fritchey
Every Database Administrator, developer, report writer, and anyone else who writes T-SQL to access SQL Server data, must understand how to read and interpret execution plans. This book leads you right from the basics of capturing plans, through how to interrupt them in their various forms, graphical or XML, and then how to use the information you find there to diagnose the most common causes of poor query performance, and so optimize your SQL queries, and improve your indexing strategy.
2017-02-02
19,120 reads
SQL Server Performance Dashboard Reports
Setting up SQL Server Management Studio (SSMS) based performance dashboard driven off servers that are registered through a Central Management Server (CMS).
2017-02-02 (first published: 2015-08-20)
15,977 reads
The Effect of NOLOCK on Performance
Using hints in a query is something that most DBAs don't ever seem to bother with, but when they do, NOLOCK seems to be their hint of choice. Wayne Fillis brings us a detailed examination of how this particular hint actually affects the performance of your system.
2017-02-02 (first published: 2007-01-24)
72,428 reads
Understanding Graphical Execution Plans - Part 3: Analyzing the Plan
Learn how to examine and read a SQL Server execution plan in this article. This is the third part of a short series from Darren White that examines execution plans and imparts the basics on an important skill for DBA's and SQL developers alike.
2017-02-02 (first published: 2014-02-25)
20,309 reads
Using A Block Predicate to Restrict Row Updates and Inserts
If you are using row level security in SQL Server 2016 you might find users are updating or inserting rows of data that keep them from seeing the row after they have performed the update or insert statement. If you want to prevent this from occurring, you can use a blocking predicate.
2017-02-02
6,585 reads
2017-02-01
188 reads
Introducing Minion CheckDB by MinionWare
Minion CheckDB completes the MinionWare maintenance and backups suite in style. Each solution is plug-and-play for the busy DBA, and deeply configurable for those shops with in-depth needs.
2017-02-01
732 reads
The Future is Now - An Internet of Things Infographic
A look at the positive and negative aspects of IoT in this infographic.
2017-02-01
248 reads
Blogs
T-SQL Tuesday #192: What career risks have you taken?
By James Serra
I’m honored to be hosting T-SQL Tuesday — edition #192. For those who may...
AI: Blog a Day – Day 3: LLM Models – Open Source vs Closed Source
By Vinay Thakur
Continuing from Day 2 , we learned introduction on Generative AI and Agentic AI,...
How to Parameterize Fabric Linked Services in Azure Data Factory for Azure Devops Deployment
Quite the title, so let me set the stage first. You have an Azure...
Forums
how to write this query?
hi everyone I am not sure how to write the query that will produce...
Rollback vs. Roll Forward
Comments posted to this topic are about the item Rollback vs. Roll Forward
Foreign Keys - Foes or Friend?
Comments posted to this topic are about the item Foreign Keys - Foes or...
Question of the Day
Fun with JSON I
I have some data in a table:
CREATE TABLE #test_data
(
id INT PRIMARY KEY,
name VARCHAR(100),
birth_date DATE
);
-- Step 2: Insert rows
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT *
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t; See possible answers