Schemas may be largely irrelevant to small databases, where it is no trouble to assign permissions to individual objects, but they are vital for a hard working corporate database that is being actively developed and used by several applications, with thousands of objects that must be assigned the correct permission.
Testing our applications is important, but at what level do we need to test? Steve Jones talks about unit testing today, and wonders if this is prevalent for SQL Server developers.
We asked DBAs to share their worst days. Some are funny, others tragic, many both. Here are the 5 finalists, vote for your favorite story to be THE worst day as a DBA.
If your database server is in Azure, then it makes sense to do backups into Azure too. SQL Server 2014 supports backups to the cloud, and particularly well with Managed Backup. Once your backups are safely in an Azure BLOB, then what? Mike Wood takes up the story.
Part 3 of Hugh Scott's series on automating sliding window partitions in SQL Server using PowerShell
The handling of dates in TSQL is complex - when SQL Server was Sybase, it was forced by the lack of prevailing standards in SQL to create its own ways of processing and formatting dates and times. Joe Celko looks forward to a future when it is possible to write standard SQL date-processing code with SQL Server.
Easily grant exec permission to all stored procedures to a database role in SQL 2005 or higher.
Much of the data collected by companies is being sold for profit. This data isn't treated well and while not much may change, perhaps we should be aware of how we handle data as professionals.
If you need to keep tabs on a number of servers and applications in a Windows domain then performance counters provide the bedrock of information. It is important to identify the counters you need and gather baseline data to allow you to create alerts when abnormal conditions occur.
By Brian Kelley
I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...
EightKB is back again for 2026! The biggest online SQL Server internals conference is...
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
Hi all, I just started using VS Code to work with DB projects. I...
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
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