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,809 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,422 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)
32,959 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,697 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,046 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,881 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,386 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
15,989 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,784 reads
Sp_readerrorlog can read any file on the hard disk, not just error logs. Read on to learn how!
2002-02-05
1,157 reads
Every organization I talk to has the same problem dressed up in different clothes....
By DataOnWheels
I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
Comments posted to this topic are about the item The day-to-day pressures of a...
Comments posted to this topic are about the item Using OPENJSON
Comments posted to this topic are about the item Data Modeling with dbt for...
I have some data in a table that looks like this:
BeerID BeerName brewer beerdescription 1 Becks Interbrew Beck's is a German-style pilsner beer 2 Fat Tire New Belgium Toasty malt, gentle sweetness, flash of fresh hop bitterness. 3 Mac n Jacks Mac & Jack's Brewery This beer erupts with a floral, hoppy taste 4 Alaskan Amber Alaskan Brewing Alaskan Brewing Amber Ale is an "alt" style beer 8 Kirin Kirin Brewing Kirin Ichiban is a Lager-type beerIf I run this, what is returned?
select t1.key
from openjson((select t.* FROM Beer AS t for json path)) t1 See possible answers