Practical Database Change Management (Part 2)
The final article on Change Management examines the more technical aspects of Change Management.
2009-06-25
3,251 reads
The final article on Change Management examines the more technical aspects of Change Management.
2009-06-25
3,251 reads
This article talks about an easy way to add hundreds of unit tests in your solution using SQL Load Test from Codeplex.
2009-04-08
9,754 reads
Developers can get so used to relying on computers for everything that they can forget how useful it can be in the design process to elicit and refine ideas whilst working in groups, using a sketchbook, pencils and crayons. Sometimes we all need a jolt to force us to take a different approach to solving software design problems.
2008-08-29
3,357 reads
When a team is developing a database application, it is a mistake to believe that deployment is a simple task. It isn’t. It has to be planned, and scripted. Alexander Karmanov describes many of the problems you’re likely to meet, and provides an example solution that aims to save the DBA from the nightmare complexity of an unplanned deployment.
2008-07-01
3,321 reads
Continuing on with his series on building a game in SQL Server, Steve Fibich talks about some more of the tables and the data they contain.
2008-07-01
2,679 reads
SQL Server expert David Poole discusses how teams can work together and share templates in Management Studio.
2014-11-27 (first published: 2008-05-20)
10,257 reads
The need to test a program that accesses and manipulates a back-end SQL Server® database is very common. In many such cases, the application interacts with the back-end data through the use of SQL stored procedures. In this type of scenario, you can think of the stored procedures as auxiliary methods of the system under test; and they must therefore be tested just like any other module in the system.
2008-05-08
4,526 reads
SQL Server source code analysis and management add database security by debugging and testing SQL applications. Learn about SQL source code analysis.
2008-05-06
2,617 reads
Greg Larsen looks at one way to design your database connection strategy to simplify changing application connections so you can plug-n-play databases with less administrative overhead when the need arises.
2008-04-28
3,880 reads
Continuing on with his series on building a game in SQL Server, Steve Fibich expands the schema and objects in this article.
2008-04-16
3,110 reads
By HeyMo0sh
Over time, I’ve realised that one of the hardest parts of cloud management isn’t...
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...
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