SQLServerCentral Editorial

Merry Christmas 2020

Merry Christmas today. Happy Holidays to all of you, for whichever holiday you celebrate this time of year. It's been a long, hard year, but I hope you are healthy and happy as we close out 2020. Hopefully next year is more enjoyable for all of us.

SQL Server execution-plans-3 book cover

Free eBook: SQL Server Execution Plans, Third Edition

If a query is performing poorly, and you can't understand why, then that query's execution plan will tell you not only what data set is coming back, but also what SQL Server did, and in what order, to get that data. It will reveal how the data was retrieved, and from which tables and indexes, what types of joins were used, at what point filtering, sorting and aggregation occurred, and a whole lot more. These details will often highlight the likely source of any problem.

Blogs

From OLTP to Analytics: Bridging the Gap with Modern SQL Architectures

By

In the beginning, there was OLTP – Online Transaction Processing. Fast, reliable, and ruthlessly...

Solving SQL Server Mysteries with a Whole Gang of Sleuths -Scooby Dooing Episode 4

By

One thing I’ve always loved about the Scooby-Doo cartoon is that he never solved...

SQL Server Availability Groups

By

Flexibility and Scale at the Database Level When SQL Server 2012 introduced Availability Groups...

Read the latest Blogs

Forums

SQL Server 2025 Jobs

By Do

Hello SQL Server 2022 16.0.4212.1 running on a Windows Server 2025 Std,V 24H2, SO...

how to optimise whole database full of table and sp in one go using githubcopilo

By rajemessage 14195

i have subscription of github copilot which i can access in vs 2022 comunity...

Password Guidance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Password Guidance

Visit the forum

Question of the Day

Using table variables in T-SQL

What happens if you run the following code in SQL Server 2022+?

declare @t1 table (id int);

insert into @t1 (id) values (NULL), (1), (2), (3);

select count(*)
from @t1
where @t1.id is distinct from NULL;
 

See possible answers