Deploying Databases From Visual Studio Team System Database Edition
With the GDR release, a whole new set of deployment functionality has become available to VSTS: DB.
2009-06-24
5,533 reads
With the GDR release, a whole new set of deployment functionality has become available to VSTS: DB.
2009-06-24
5,533 reads
A description of the things to avoid and do when involved with a beta test.
2008-09-26
2,895 reads
An overview of how to collect data from TSQL into Operations Manager Performance Rules.
2008-06-05
7,074 reads
Longtime SQL Server DBA and author Grant Fritchey decided to quiz his developers on how to perform some simple functions in T-SQL. Read about his results and see how you might do in taking his quiz.
2008-05-01 (first published: 2007-05-28)
18,502 reads
The trials and tribulations of our first attempt using Virtual Servers
2008-04-08
7,656 reads
In order to support multiple environments, a number of choices, not readily apparent, need to be made. This article outlines one approach that is working.
2008-01-24
3,491 reads
Testing is an important part of any software development process, but it's a part that many of us skimp on or ignore because of the tedious nature of testing. Longtime author Grant Fritchey has been working with Visual Studio Team Edition for Database Professionals and has written us an article on how you can make your unit testing easier.
2008-01-16 (first published: 2007-02-01)
7,856 reads
Testing is an important part of programming and it is no different with SQL Server development. Longtime author Grant Fritchey brings us a look at the new testing features available in Visual Studio 2005.
2006-11-15
9,949 reads
One of the fundamental skills a developer needs is the ability to test their code. Most people don't really do a good job, partly because they don't have a good process and leave testing until the end. Grant Fritchey brings us a new method of unit testing T-SQL stored procedures that can help you build automated tests for your code.
2006-06-20
17,775 reads
Working with outer joins can be tricky since the syntax doesn't always appear to make sense. Grant Fritchey brings us a great example of how this confusion can cause issues if you use the old style syntax.
2006-05-15
15,143 reads
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...
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