Having been at the sharp end of many successful SQL Server solutions, I believe there are some fundamental principles that all successful SQL Server installations have in common. Whilst the challenges in delivering an enterprise-scale database-intensive application can be wide and varied, there are a few basic practises that will give you the best possible chance of success.
his white paper covers some of the operational and administrative tasks associated with SQL Server 2005 security and enumerates best practices and operational and administrative tasks that will result in a more secure SQL Server system.
In the previous articles, Jacob Sebastian looked at using XML to save a sales order with variable numbers of line items to a SQL Server
2000 database. In this part, he expands upon the processing to access that data from multiple nodes.
This article introduces some techniques that will allow you to pinpoint exactly where the performance issues are in your system, so you'll know exactly where to spend your time (and money) in solving them.
Dan Sullivan continues his exploration of the versatile PowerSMO tool with coverage of how to control logins, monitor server activity and create standalone administrative scripts.
I regularly use SQLIO.EXE to gauge the maximum throughput a disk subsystem can sustain. Recently Microsoft released SQLIOSIM.EXE to provide better results for this type of test. However they didn't release any documentation on the tool and I could never figure out what it was trying to tell me. It looks like they finally did release a Knowledge Base article on SQLIOSIM. Give it a spin. I'd be curious to hear what you think of the tool.
In part 2 of this series, Jacob Sebastion continues looking at XML in SQL Server 2000 with some advanced XML processing.
Diagnose performance problems in MSSQL Server 2005 with a powerful new administration tool. BI Architect Bill Pearson provides hands-on guidance in installing and using this powerful new dashboard / report pack, freely available to MSSQL Server 2005 users everywhere.
SQL Server 2005 has changed replication dramatically and one of the changes is that subscriber tables have the identity
column. SQL Server guru Andy Warren takes a look at what impact this has on transactional replication.
Robyn Page and Phil Factor demonstrate some set-based techniques for string manipulation and time interval-based reporting, which use helper tables rather than iterative logic or the dreaded cursor.
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