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.
2008-02-29 (first published: 2005-08-08)
119,756 reads
SQL Server has some great solutions for writing reports easily, ensuring quick service for your customers. However many of the quick ways of generating reports from the database include the column headers in the results. And often clients who expect customized work want to see labels that are more familiar to them. Leo Peysakhovich has developed a way that allows him to easily return custom labels from his stored procedures.
2004-10-14
5,821 reads
Error handling is one of those things that is simple to do in SQL Server, but most people don't do it and it's not the most rebust thing. Here's another way that you can implement error handling in your stored procedures from a new author Amit Jethva.
2004-04-27
21,455 reads
Regular columnist Robert Marda writes about the basics of using output parameters. If you're not using output params we hope this article will get you started - they are a great way to return less data to the client, perfect if you need only a few values and not a recordset/resultset.
2007-10-26 (first published: 2003-11-25)
33,057 reads
Regular columnist Robert Marda discusses a few ideas on stored procedure documentation. How much documentation do you need and is "documentation" different than code comments?
2003-10-20
18,739 reads
This month Robert covers the process he uses for developing stored procedures. In many ways it reflects how software is developed, but it does have it's minor differences. This is a high level process discussion, not a line by line example of the entire process - by design of course.
2003-09-03
11,095 reads
Return values from stored procedures (not output params, true return values) probably aren't used as often as they should be. Robert gives you some good examples of how to use them.
2003-08-05
9,902 reads
Should your stored procedure continue when it hits an error? Or keep executing? What errors will cause a stored procedure to quit executing auotmatically? Regular columnist Robert Marda has at least some of the answers, we think you'll find this interesting.
2003-06-26
7,403 reads
This article introduces TSQLDoc, a Windows Script Host script that extracts procedure metadata and embedded documentation comments from Transact-SQL stored procedures, generates XML documentation for every stored procedure in a database and optionally transforms the XML document into HTML or other format using XSLT.
2002-08-09
16,029 reads
Here's a general overview for creating and editing stored procedures. Head over to the discussion forum for this article and present your creative ideas for using this powerful feature of SQL Server to the SSC community.
2002-05-27
19,821 reads
By Steve Jones
Thanks for attending my sessions. Resources below: Slides: Using Data API Builder GitHub repo: ...
By Steve Jones
Thanks to everyone that attended my sessions at VS Live San Diego yesterday. It...
By Steve Jones
I was creating a question on sp_readerrorlog and realized that this procedure is different...
When I run my query from DW, which uses a linked server, it times...
Comments posted to this topic are about the item Implementing Type 4 Slowly Changing...
Comments posted to this topic are about the item The Disabled Index
I run this code on SQL Server 2022.
CREATE TABLE Drink
(
drinkid INT NOT NULL
CONSTRAINT DrinkPK PRIMARY KEY CLUSTERED,
drinkname VARCHAR(20),
rating NUMERIC(2, 1)
)
GO
INSERT INTO Drink
(
drinkid,
drinkname,
rating
)
VALUES
(1, 'Margarita', 4.5),
(2, 'Mojito', 4.3),
(3, 'Old Fashioned', 4.7),
(4, 'Martini', 4.4),
(5, 'Cosmopolitan', 4.2)
GO
ALTER INDEX drinkpk ON dbo.drink DISABLE
GO
SELECT * FROM dbo.Drink
GO
What is the result? See possible answers