In the future we may be required to bring our own devices to work. Does that make sense? Would you want to get an allowance and purchase your own laptop?
When replicating data to other servers it is always a concern that the subscribers may be far behind. In this article, Tim Smith shares some queries to help monitor SQL Server replication row counts.
SQL Server instances are generally poorly-documented. How easily can you tell if something has changed? How easily can you check that there is adequate space for growth? Are you up-to-date with licenses? What errors are happening? Who has accessing the system? Before PowerShell, it was difficult to be on top of all this. Now you can, with the help of Sander's database documenter.
Is it worth automating things? Many people say yes, but Steve Jones says it isn't just about time saved.
Whenever a query is executed in SQL Server, its execution plan, as well as some useful execution data are placed into the plan cache for future use. This information is a treasure trove of metrics that can allow some very useful insight into your server’s performance and resource consumption - Ed Pollack shares some useful queries to start utilizing it.
There was an announcement last week that SQL Server can run on Linux. And it's coming next year.
Virtual Chapter meeting, Mar 16, 12pm EST. Documentation is mostly overlooked and only comes up when a problem arises. What if you'd have a tool or method to generate documentation for all your database servers? In this session, Sander Stad will show you show how easy it is to use PowerShell to retrieve information from your servers. He'll detail what can be used to document your servers, how to retrieve the information and what should be documented. In the end you no longer have an excuse not to document your servers.
Erin Stellato (@erinstellato) looks into sparse columns in SQL Server – the changes to space requirements and the impact on the write portion of your workload.
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
By Steve Jones
Finding duplicates was an interview question for me years ago, and I’ve never forgotten...
By HeyMo0sh
Over time, I’ve realised that one of the hardest parts of cloud management isn’t...
Comments posted to this topic are about the item Fun with JSON II
Comments posted to this topic are about the item Changing Data Types
Comments posted to this topic are about the item Answering Questions On Dropped Columns
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 t1.[key] AS row,
t2.*
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t1
CROSS APPLY OPENJSON(t1.value) t2; See possible answers