On The Road Again...Part I
An interesting interview with Raj Gill, SQL Server 2005 Roadshow Presenter by Robert Pearl. Get inside the mind of the co-founder of Scalability Experts.
An interesting interview with Raj Gill, SQL Server 2005 Roadshow Presenter by Robert Pearl. Get inside the mind of the co-founder of Scalability Experts.
SQL Server 2005 brings many new features, but one of the most popular and hotly contested is the integration of the CLR inside the database server. New author Anajwala brings us a Hello World and an example stored procedure written using C#.
Ensuring your SQL Server is performing well is a large part of any good DBA's job. It is not just writing good queries, but also monitoring your server and getting alerts on critical issues. Mike Metcalf has brought us a great article that shows how you can setup performance alerts and be notified via SMTP.
SQL Server 2000 introduced user-defined functions (UDFs), and they were immediately hailed as a great tool for encapsulating repetitive code, as well as allowing you to perform more complicated processing directly in an SQL expression. On its face, that claim is valid. You can certainly improve readability and maintainability with UDFs. But cleaner code will be cold comfort if your queries bog down and lock up your server.
One of the less exciting, but perhaps very powerful new features in SQL Server 2005, the Service Broker is an asynchronous communications method. MVP Srinivas Sampath brings us the second part of his series looking at what you can accomplish with a practical example.
How much backup data should you keep around and what are the implications? Part 2 of a series looking at backups and their implications.
DTS was one of the most amazing new features of SQL Server 7 and in SQL Server 2005 it has been renamed to Integration Services. This component has some incredible new capabilities, many of which come at a steep learning curve. New author Kristian Wedberg brings us a basic article and some code on how you can SSIS to generate test data.
SQL Server Database administrators often generate SQL Statements and execute the generated SQL statement in order to simplify certain tasks. It has always been a twin operation. This article illustrates how to use un-documented stored procedures to execute the generated SQL Statements directly.
We've had a lot of coverage of dynamic sql (including another great one from Robert Marda later this week) but this one is a little different. Done in a question/answer format, Andy tries to explain to junior developers why dynamic sql is to be avoided, how to do so, what to do when you can't.
Newly surfaced Tableau Software aims to revolutionize the acquisition and deployment process with its product suite, Tableau Professional and Standard Editions. To a significant degree, it has succeeded...
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