You may come across or even inherit a system where many of the users have different default schemas. Usually, this is easy to remedy - you go into Management Studio, right-click the user, and change the default schema through the UI. Or you write an ALTER USER command manually. But what if you have hundreds of users, across all of your user databases, that should all have the same default schema?
SQL Saturday is a free day of SQL Server training and networking coming to Washington DC on December 7. Paid pre-con sessions for this SQL Saturday are available.
Today Steve Jones talks about some of the problems in SQL Server. Should we be documenting the situations in which features don't work well?
In this series on implementing data services in Azure, Marcin Policht turns his attention to the remediation of incompatibilities resulting from of limitations inherent to Platform as a Service (PaaS) based deployments, which will need to be addressed as part of the migration process.
Steve Jones knows that good development practices require lots of skill and practice, but the basis for stability with your code is version control. He talks about some reasons why you might want to implement it.
For loading text, CSV or XML files into SQL Server, the Log Parser utility, with its amazing SQL engine, is likely to be the obvious choice. Although initially developed purely for converting IIS logs, the Log Parser can turn its hand to a range of formats including even event logs or the Windows registry.
A CLR Procedure that performs multi-threaded fie copies without external command line tools.
How can you measure someone's DBA skills? Steve Jones comments on a new technique that someone suggested to him.
Understanding indexes and how they work can be complicated enough for a Jr. DBA, but throw in all the different options and properties and an index can soon be overwhelming. Brady Upton takes an introductory look at creating an index in SQL Server using SQL Server Management Studio. He explains what each index property is meant for and the various options presented.
Introduction into Locking, Blocking and Deadlocks in SQL Server, and why SQL Server uses these actions.
By HeyMo0sh
One of the biggest challenges I’ve faced in cloud operations is maintaining clear visibility...
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
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