Undocumented Extended and Stored Procedures
Some useful undocumented extended and stored procedures in SQL Server 2005
2009-11-20 (first published: 2008-05-09)
33,453 reads
Some useful undocumented extended and stored procedures in SQL Server 2005
2009-11-20 (first published: 2008-05-09)
33,453 reads
Building an application with modular programming not only speeds development, but can make for a more stable application. New author Sreeju Jumar brings us a look at how you can further modularize your stored procedures.
2008-04-29
11,940 reads
Different ways of passing sets of data between stored procedures.
2008-04-08
7,906 reads
2008-02-25 (first published: 2008-01-15)
930 reads
In the first article of a new series on T-SQL tips, Jacob Sebastian brings us a very useful technique. How to pass a table to a stored procedure so some set of rows can be operated on using some business logic.
2008-05-02 (first published: 2007-05-30)
69,549 reads
In the fourth installment of this series, Jacob Sebastian moves on to SQL Server 2005 and the new XML capabilities that make
working with XML data easier than ever.
2007-04-05
12,864 reads
Grant Fritchey steps into the workbench arena, with an example-fuelled examination of catching and gracefully handling errors in SQL 2000 and 2005, including worked examples of the new TRY..CATCH capabilities.
2007-03-06
3,580 reads
While the strength of SQL Server is not in string manipulation, it can be very handy when backing a web site to be able to automatically include links for some of your content. New author Grey Wilson brings us an easy technique to easily deliver results to developers with URLs embedded inside.
2006-08-08
6,358 reads
T-SQL has some well known limitations when working with parameters for a stored procedure, not the least of which is a variable number of parameters. While there are some solutions, they can be cumbersome to work with. Sloan Holliday brings us a creative solution using XML that can solve many issues.
2006-02-28
12,063 reads
It seems that SQL Server developers avoid stored procedures whenever possible, especially if they are new to the product. Kathi Kellenberger brings us a basic article that you can give to developers that explains the basics of how you use parameters with ADO.NET, especially output parameters.
2019-05-23 (first published: 2005-08-08)
119,693 reads
By Vinay Thakur
Continuing from Day 3 where we covered LLM models open/closed and their parameters, Today...
By Steve Jones
One of the nice things about Flyway Desktop is that it helps you manage...
By HeyMo0sh
Microsoft Fabric (not to be confused with the more general term “fabric” in DevOps)...
I'm fairly certain I know the answer to this from digging into it yesterday,...
Hi Team, I am trying to refresh the Azure Synapse Dedicated pool from production...
hi everyone I am not sure how to write the query that will produce...
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 *
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t; See possible answers