The Backup Myth (MP3)
Running backups is enough for disaster recovery, right? That's a myth that could get you into trouble. Steve Jones explains there's more that's needed.
2008-01-08
641 reads
Running backups is enough for disaster recovery, right? That's a myth that could get you into trouble. Steve Jones explains there's more that's needed.
2008-01-08
641 reads
Running backups is enough for disaster recovery, right? That's a myth that could get you into trouble. Steve Jones explains there's more that's needed.
2008-01-08
296 reads
Tony Davis offers his congratulations on a new MVP at SQLServerCentral.com and DatabaseWeekly.com.
2008-01-07
56 reads
As a SQL Server DBA you should know that your code is stored in syscomments by default. While most DBAs use version control systems, there are times you might want to look through the code on the server for comparison purposes. Robert Cary brings us an article on how you can do this in 2000 and 2005.
2008-01-07 (first published: 2007-01-22)
8,418 reads
Learn how to use an Analysis Services cube as a data source by using parameterized MDX queries, as well as how to localize label strings in a report, in SQL Server 2005.
2008-01-07
2,399 reads
SQL Server 2005 provides four methods of encryption. Part one of this article covers encryption and decryption by passphrase.
2008-01-07
3,647 reads
2008-01-04 (first published: 2003-09-26)
185,360 reads
The I/O system is important to the performance of SQL Server. When configuring a new server for SQL Server or when adding or modifying the disk configuration of an existing system, it is good practice to determine the capacity of the I/O subsystem prior to deploying SQL Server. This white paper discusses validating and determining the capacity of an I/O subsystem. A number of tools are available for performing this type of testing. This white paper focuses on the SQLIO.exe tool, but also compares all available tools. It also covers basic I/O configuration best practices for SQL Server 2005.
2008-01-04
3,111 reads
Business Intelligence Architect Bill Pearson introduces the useful .AllMembers function, reinforcing the basic concepts, as always, with hands-on practice examples.
2008-01-04
2,173 reads
An exploration of the process of translating a conceptual model to a logical model, and ultimately, a faithful implementation using T-SQL.
2008-01-03
2,852 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