A short survey from Microsoft looking for feedback from users in order to try and improve the application development process. If you build applications with MS technolgies, especially SQL Server, take a moment and respond.
SQL Server has a rock solid backup and restore routine. However, it is not the most efficient way of handling the backups and restores. Neither in terms of time or space required. A number of software vendors have developed their own additions to SQL Server that accelerate or compress the backups (or both). Wesley Brown has taken four of these products into his environment and run some comparisons. Read about large databases in part 2 of this series.
SQL Server depends heavily on good indexing to perform well. The optimizer requires relevant and intelligent indexing in order to do its job well. Author Andre Vigneau brings us a script that he uses to detect possible index problems in the database design as well as a number of hints to ensure that your database is performing optimally.
SQL Server has a rock solid backup and restore routine. However, it is not the most efficient way of handling the backups and restores. Neither in terms of time or space required. A number of software vendors have developed their own additions to SQL Server that accelerate or compress the backups (or both). New Author Wesley Brown has taken four of these products into his environment and run some comparisons. Read part one of his review.
With some recent hubub and questions, Steve Jones decided to spend a few moments welcoming everyone to the community and give some background on what this site is all about.
SQL Server clusters are great tools to ensure that your servers are highly available. However there are some times when you'll want to manually perform a failover for testing, maintenance, etc. New author Anthony Bressi brings you a technique and code to allow you to use VB 6.0 to build a small program to automatically do this.
If you are running Microsoft SQL Server databases to support critical enterprise applications, you are part of a growing trend. The cost/performance benefits of Microsoft SQL Server on the Microsoft Windows NT and Windows 2000 platforms have fueled the growth of SQL Server as a platform for enterprise-class applications.
Transactions in SQL Server are probably no more complicated than those in other RDBMS products, which is to say they are fairly complex. Don Peterson continues with part 3 of his series and takes a look at transaction isolation levels and how they interact with multiple connections and their impact on locking.
This is the twenty-fifth article of the series, MDX Essentials. The series is designed to provide hands-on application of the fundamentals of the Multidimensional Expressions (MDX) language, with each tutorial progressively adding features designed to meet specific real-world needs.
SQL Server 2000 is easy to administer relative to other RDBMS, but there is still plenty of room for improvement. Author Andre Vigneau has built a database toolkit to allow him to manage his cross platform databases. This is the second article in his series and deals with establishing connections to any database platform.
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