New Feature: Playlist Center! Pick a topic and let our playlists guide the way.

Easy-to-follow video tutorials help you learn software, creative, and business skills.Become a member

Returning data using data sets

From: SQL Server: Triggers, Stored Procedures, and Functions

Video: Returning data using data sets

Now I'd like to talk about returning data through stored procedures, specifically returning data as datasets primarily. We'll also talk a little bit about a return value. I have some code on the screen here that is available in our exercise files. This is very similar to what we were doing in the previous section. It's code that allows us to modify a stored procedure and execute that stored procedure. I'm going to modify the stored procedure to have a return value. So at the end, the very last thing before the end statement, I will simply issue the keyword Return, and give it a numeral.

Returning data using data sets

Now I'd like to talk about returning data through stored procedures, specifically returning data as datasets primarily. We'll also talk a little bit about a return value. I have some code on the screen here that is available in our exercise files. This is very similar to what we were doing in the previous section. It's code that allows us to modify a stored procedure and execute that stored procedure. I'm going to modify the stored procedure to have a return value. So at the end, the very last thing before the end statement, I will simply issue the keyword Return, and give it a numeral.

So in this case, Return 1. When we execute that, we will likely not see that one returned just yet, we have to go through a little more effort to actually see what is returned. We will declare a variable to hold that value. We will then execute the stored procedure, and take what is returned, and store it in our newly created variable, and then we'll need one last line of code to display that returned value.

Go ahead and execute all of that, and so we see we got two results in the Results pane at the bottom; one says, Hello World, this is fun which is the data returned from the stored procedure, and then also the numeral that we returned, and in this case, we returned 1. We could change that easily to return a different numeral and now it returns 12. Microsoft recommends as a best practice every stored procedure should return a value. Typically you return either 0 or 1 for success or failure.

So if the stored procedure failed for some reason, you would return a 0, if it was successful, you would return 1. Different people like to have a little different naming conventions for that. For example, if the stored procedure returned an error, you could return a code that signifies an error in your mind, maybe something like -1. But the bottom line is Microsoft recommends, and I also agree with this recommendation, the last line of every stored procedure should be returned a numeral to me, and that numeral should have some meaning.

Beyond returning numerals, you probably want your stored procedure to return some data. And we've been doing that; we have Select, and then we're returning some text. We can return multiple datasets by having multiple SELECT statements. So I'll have a second SELECT statement that will return a second set of data. Now at the bottom, we see that we return three different things; the first data set, below that the second dataset, and then finally the return value.

You could additionally add a third dataset, a fourth dataset, a fifth dataset. The machine does not put an upper limit on what we can and cannot return. Good common sense says, you probably want to limit what one stored procedure returns, but two or three datasets is not uncommon. Notice I said that the return -1 or return whatever numeral you have should be the last line of the stored procedure. Let's see what happens if you violate that recommendation, and we put that in the middle right here.

You notice it returned the first dataset, "Hello World this is fun." It returned the -1, it did not return the phrase "This is more text." The machine stops returning after the line with the keyword RETURN. It will perform the return on that line. It will not do any returns after that. So the keyword RETURN almost always needs to be the very last thing in your stored procedure. So in this demonstration, we've seen returning data from a stored procedure as either a numeral or a dataset.

In our next video, we'll talk about returning data as a cursor.

Show transcript

This video is part of

Image for SQL Server: Triggers, Stored Procedures, and Functions
 
Expand all | Collapse all
  1. 2m 15s
    1. Welcome
      51s
    2. What you should know
      51s
    3. Using the exercise files
      33s
  2. 11m 1s
    1. Comparing triggers, functions, and procedures
      3m 25s
    2. Why use a stored procedure?
      4m 59s
    3. Why use functions?
      1m 27s
    4. Why use triggers?
      1m 10s
  3. 6m 2s
    1. Configuring your environment
      4m 53s
    2. Downloading and installing a sample database
      1m 9s
  4. 26m 25s
    1. Creating a stored procedure
      2m 46s
    2. Modifying a stored procedure
      2m 34s
    3. Returning data using data sets
      3m 45s
    4. Returning data using cursors
      3m 45s
    5. Using input and output parameters
      5m 24s
    6. Using security and permissions
      5m 24s
    7. Using transactions
      2m 47s
  5. 11m 56s
    1. Creating a user-defined function
      4m 59s
    2. Exploring single-value functions
      4m 18s
    3. Exploring table value functions
      2m 39s
  6. 9m 31s
    1. Using "after" triggers
      3m 47s
    2. Using "instead of" triggers
      2m 9s
    3. Using nested triggers
      1m 38s
    4. Using database-level triggers
      1m 57s
  7. 12m 43s
    1. Exploring a real-world INSERT procedure
      5m 32s
    2. Exploring a real-world UPDATE procedure
      3m 13s
    3. Implementing logging on DELETE
      3m 58s
  8. 19m 38s
    1. Understanding the Common Language Runtime (CLR) and the .NET framework
      1m 52s
    2. Using CLR with SQL Server 2012
      4m 11s
    3. Writing stored procedures with C# .NET
      5m 51s
    4. Writing functions with .NET
      5m 7s
    5. Choosing between T-SQL vs. CLR
      2m 37s
  9. 11m 34s
    1. Creating a basic web form and connecting to a database
      2m 56s
    2. Executing a stored procedure
      2m 4s
    3. Passing parameters
      3m 41s
    4. Getting return values
      2m 53s
  10. 1m 43s
    1. Next steps
      1m 43s

Start learning today

Get unlimited access to all courses for just $25/month.

Become a member
Sometimes @lynda teaches me how to use a program and sometimes Lynda.com changes my life forever. @JosefShutter
@lynda lynda.com is an absolute life saver when it comes to learning todays software. Definitely recommend it! #higherlearning @Michael_Caraway
@lynda The best thing online! Your database of courses is great! To the mark and very helpful. Thanks! @ru22more
Got to create something yesterday I never thought I could do. #thanks @lynda @Ngventurella
I really do love @lynda as a learning platform. Never stop learning and developing, it’s probably our greatest gift as a species! @soundslikedavid
@lynda just subscribed to lynda.com all I can say its brilliant join now trust me @ButchSamurai
@lynda is an awesome resource. The membership is priceless if you take advantage of it. @diabetic_techie
One of the best decision I made this year. Buy a 1yr subscription to @lynda @cybercaptive
guys lynda.com (@lynda) is the best. So far I’ve learned Java, principles of OO programming, and now learning about MS project @lucasmitchell
Signed back up to @lynda dot com. I’ve missed it!! Proper geeking out right now! #timetolearn #geek @JayGodbold

Are you sure you want to delete this note?

No

Thanks for signing up.

We’ll send you a confirmation email shortly.


Sign up and receive emails about lynda.com and our online training library:

Here’s our privacy policy with more details about how we handle your information.

Keep up with news, tips, and latest courses with emails from lynda.com.

Sign up and receive emails about lynda.com and our online training library:

Here’s our privacy policy with more details about how we handle your information.

   
submit Lightbox submit clicked
Terms and conditions of use

We've updated our terms and conditions (now called terms of service).Go
Review and accept our updated terms of service.