Detailed error reporting from stored procedures can be extremely valuable when debugging problems in your application. I will share different levels of detail that you can build into your stored procedures. You can choose the level of detail appropriate for your situation.
2005-01-25
2,903 reads
Here's a short script to generate a random alphanumeric string based on newid(). The procedure takes in length (@len) which determines the key length. Length must be between 8 and 32. Result is returned in an output parameter. A test script is supplied.
2005-01-24 (first published: 2005-01-10)
1,281 reads
Table partitioning is a powerful new feature in SQL Server 2005. It is primarily a manageability feature, but my interest here is in the performance and scalability of table and index partitioning for use with very large tables.
2005-01-24
1,462 reads
Desc : This SQL statement will provide script for backup all your jobs.Remark : Grow-up 'maximum characters per column' (for 8192) and disable 'print column headers' in 'tools' / 'options'
2005-01-21 (first published: 2005-01-11)
1,057 reads
Databases are being stolen. Customer data, credit card data, taxpayer data - they're all vulnerable. Scary? Yes - but wait, there's more. It's not just "their" data that's vulnerable - it's ours too!
2005-01-21
2,107 reads
Fabian Pascal, famed database author and writer takes his shots at a recent thread on another SQL site. He makes some good points about normalization.
2005-01-20
3,074 reads
SQL Server 2005 has added a new format for queries called a Common Table Expression or CTE. CTE’s are part of the SQL:1999 Specification and represent further compliance with this specification by SQL Server. This article will cover using one of the many capabilities of CTE’s, implementing recursive functions. A recursive function is a one that iteratively executes itself. Understanding how CTE’s implement recursive functions is the first step to understanding the full capabilities of CTE’s.
2005-01-19
1,858 reads
When it comes to auditing index use in SQL Server databases, I sometimes get overwhelmed. For example, how to do you go about auditing indexes in a database with over 1,500 tables? While auditing a single index is relatively straight-forward, auditing thousands of them in multiple databases is not an easy task. Whether the task is easy or not, it is an important task if you want to optimize the performance of your SQL Server databases.
2005-01-18
3,860 reads
ActiveX Script that will rename all DTS Package Tasks and Steps to include the Task Description. For generating DTS Logs with meaningful names.
2005-01-17 (first published: 2005-01-04)
372 reads
Have you ever had to access data from either a non-SQL Server source or from a separate SQL Server database (either residing on the same instance or on a separate instance)? Rahul Sharmas discusses how to bridge the gap between two different SQL Server instances or between heterogenous RDBMS such as SQL Server and Oracle: Use linked servers!
2005-01-17
3,331 reads
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...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
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