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

Start learning with our library of video tutorials taught by experts. Get started

SQL Server 2008 Essential Training
Illustration by

Using the OUTPUT clause to return inserted keys and GUIDs


From:

SQL Server 2008 Essential Training

with Simon Allardice

Video: Using the OUTPUT clause to return inserted keys and GUIDs

It's very common that as you start inserting information into your databases, what you're going to need or at least what your applications are going to need is to find out a bit more information about what you just inserted. Particularly in the case where you are inserting information into a table that is going to generate keys for you, either identity columns like this one, ProductCategoryID just going up one by one, or guids that are being built as well or perhaps both at the same time.
Expand all | Collapse all
  1. 2m 21s
    1. Welcome
      1m 19s
    2. Using the exercise files
      1m 2s
  2. 17m 58s
    1. SQL Server core concepts
      9m 4s
    2. SQL Server editions
      3m 8s
    3. Applications included with SQL Server
      5m 46s
  3. 26m 1s
    1. Preparing for installation
      3m 44s
    2. Creating service accounts
      2m 33s
    3. Installing SQL Server
      11m 42s
    4. Post-installation checks
      3m 9s
    5. Installing sample databases
      4m 53s
  4. 13m 35s
    1. Introduction to SQL Server Management Studio
      8m 7s
    2. Introduction to SQL Server Books Online
      3m 6s
    3. SQL Server system databases
      2m 22s
  5. 1h 26m
    1. Planning your database
      9m 39s
    2. Creating a SQL Server database
      4m 7s
    3. Creating tables
      7m 51s
    4. Data types in SQL Server
      12m 25s
    5. Defining keys
      8m 9s
    6. Creating default values
      4m 39s
    7. Creating check constraints
      2m 25s
    8. Creating unique constraints
      4m 34s
    9. Introduction to relationships and foreign keys
      9m 51s
    10. Creating relationships in SQL Server Management Studio
      8m 14s
    11. Database normalization
      11m 47s
    12. Creating computed columns
      3m 10s
  6. 23m 11s
    1. Using the SQL Server Import and Export Wizard
      3m 58s
    2. Importing Excel files into SQL Server
      6m 11s
    3. Importing CSV files into SQL Server
      5m 27s
    4. Importing Access databases into SQL Server
      7m 35s
  7. 55m 29s
    1. Introduction to Transact-SQL
      3m 43s
    2. Using SELECT statements
      7m 16s
    3. Changing the default database
      2m 21s
    4. Creating conditions in SQL
      8m 10s
    5. Sorting your output
      3m 23s
    6. Using aggregate functions
      7m 12s
    7. Finding unique values
      2m 14s
    8. Joining multiple tables together
      8m 0s
    9. Using subqueries
      9m 33s
    10. Viewing execution plans
      3m 37s
  8. 19m 36s
    1. Writing INSERT statements
      5m 47s
    2. Writing UPDATE statements
      4m 38s
    3. Writing DELETE statements
      2m 54s
    4. Using the OUTPUT clause to return inserted keys and GUIDs
      6m 17s
  9. 32m 52s
    1. Introduction to SQL functions
      6m 26s
    2. Using SQL configuration functions
      2m 14s
    3. Using string functions
      7m 26s
    4. Using date functions
      6m 27s
    5. Creating user-defined functions
      10m 19s
  10. 28m 46s
    1. Introduction to stored procedures
      4m 23s
    2. Creating stored procedures
      11m 23s
    3. Introducing transactions
      4m 23s
    4. Creating transactions
      8m 37s
  11. 16m 39s
    1. Understanding and creating indexes
      6m 32s
    2. Monitoring and rebuilding indexes
      6m 0s
    3. Monitoring database size and integrity
      4m 7s
  12. 11m 41s
    1. Creating backups
      4m 21s
    2. Creating differential backups and using backup compression
      3m 40s
    3. Restoring databases
      3m 40s
  13. 17m 40s
    1. Introduction to SQL Server security and permissions
      5m 54s
    2. Adding a Windows user to the database
      5m 7s
    3. Creating SQL Server logins and switching authentication modes
      6m 39s
  14. 36m 41s
    1. Introduction to SQL Server Reporting Services
      2m 52s
    2. Connecting to the Report Manager
      4m 29s
    3. Using Report Builder
      12m 4s
    4. Formatting values in reports
      4m 17s
    5. Adding indicators to reports
      5m 11s
    6. Adding charts to reports
      3m 54s
    7. Working with report security
      3m 54s
  15. 24m 41s
    1. Introduction to SQL Server Integration Services (SSIS)
      1m 57s
    2. Using Business Intelligence Development Studio (BIDS)
      6m 59s
    3. Creating and executing a simple SSIS package
      7m 35s
    4. Importing packages into SQL Server Management Studio
      3m 21s
    5. Scheduling jobs with SQL Server Agent
      4m 49s
  16. 31s
    1. Goodbye
      31s

Watch this entire course now—plus get access to every course in the library. Each course includes high-quality videos taught by expert instructors.

Become a member
please wait ...
SQL Server 2008 Essential Training
6h 54m Beginner Dec 15, 2010

Viewers: in countries Watching now:

In SQL Server 2008 Essential Training, Simon Allardice explores all the major features of SQL Server 2008 R2, beginning with core concepts: installing, planning, and building a first database. Explore how Transact-SQL is used to retrieve, update, and insert information, and gain insight into how to effectively administer databases. The course also covers features outside SQL Server's database engine, including technologies that have grown up around it: SQL Server Reporting Services and Integration Services. Exercise files are included with the course.

Topics include:
  • Using T-SQL (Transact-SQL)
  • Managing databases with SQL Server Management Studio
  • Understanding database normalization
  • Using SELECT statements
  • Building indexes
  • Monitoring database size and integrity
  • Backing up and restoring databases
  • Creating functions and stored procedures
  • Managing database permissions
  • Creating and formatting reports
  • Adding charts to reports
  • Creating and executing a simple SSIS package
Subjects:
Business Developer Servers Databases
Software:
SQL Server
Author:
Simon Allardice

Using the OUTPUT clause to return inserted keys and GUIDs

It's very common that as you start inserting information into your databases, what you're going to need or at least what your applications are going to need is to find out a bit more information about what you just inserted. Particularly in the case where you are inserting information into a table that is going to generate keys for you, either identity columns like this one, ProductCategoryID just going up one by one, or guids that are being built as well or perhaps both at the same time.

But in the INSERT example we saw before, all that I'm inserting is a ParentProductCategoryID and a name, because the guids and the identities are being generated for us. Now, we want to get that information after this INSERT has happened. This used to be a bit of a problematic thing to do. In fact often what you used to have to do is write little pieces of code to generate that guid yourself and then insert it yourself, so that you knew what it was. Well, it's a lot simpler these days. What we just do is we take our INSERT statement and we change it just a little bit.

See, before the VALUES that we were inserting, I'm using this new clause called OUTPUT. And we can actually use this on an INSERT, we can use it on an UPDATE, we can use it on a DELETE. OUTPUT is a special kind of a unique clause here. What it allows us access to is the inserted columns that are just about to happen and it knows they haven't happened yet, but it knows that we will have them. In fact, if I say OUTPUT inserted, notice that inserted is in IntelliSense, and I hit that, I hit the dot, and that's even smart enough to tell me here in IntelliSense, "Well, you are inserting into ProductCategories, so these are your only options.

Which one would you like?" Well! Let's say that what I want to do is I want to find the ProductCategoryID that's going to be generated as an identity field. And now when I hit Execute, what happens is I don't just get the phrase "one row affected," I get the new ProductCategoryID that I just created, which was ProductCategoryID number 56. Now you can even output multiple inserted values. So I can hit comma. I want now the inserted guid that's happening there.

I have got to be careful because I'm running another INSERT statement and Commuter Bikes already inserted there and that has to be unique. So I'll just change that to Custom Bikes, hit Execute, and we get back 57, which was to be expected. And the new generated rowguid. That again is being set because there's a default constraint on the ProductCategory table that will generate a new rowguid every time. Now in essence, what's going to happen here is if you've got an application that is executing this code, it's almost like having a mini SELECT statement that returns these values afterwards.

It's just a lot easier to write. And we can see later how this might be added to and inserted into say a stored procedure to make it a bit more friendly and a bit more reusable. But this is the general idea of using OUTPUT clause. In fact, I will show you another example. If I wanted to do a DELETE, I'm going to say that I'm going to DELETE FROM, same table not surprisingly. Again usually I just put the WHERE clause. Always want a WHERE clause when I'm doing this DELETE.

So ProductCategoryID = well let's say the one that we just entered in a couple minutes ago, which was 56. And again, I'm putting in the OUTPUT clause. Well! It's not going to be inserted this time around. That doesn't make sense but I will have an OUTPUT deleted. and I can say I'd like to know what the Name was. I'd like to know what the deleted guid was. We hit Execute and it tells us the name was Commuter Bikes and that was the rowguid.

So we can get that information back as well. I try and execute that again, not surprisingly I get no output because there is no row with ProductCategoryID equal to 56 anymore. Now it can also be used on an UPDATE statement but it's probably not what you are expecting. Here's the deal. When we construct a regular UPDATE statement here such as UPDATE SalesLT.ProductCategory, of course we have to use our SET, what are we actually doing here. I am going to just do a SET parent ProductCategoryID = 1, WHERE ProductCategoryID = 57.

Now, usually you might be ahead of me, thinking well, we put the OUTPUT in here and we had an inserted. for insert and a deleted. for deleted. So presumably we have an updated. And no, we don't. Here's the deal. What that inserted word and the deleted word represent is essentially a temporary table in memory. If we do an INSERT, the inserted table represents what happened after the INSERT.

If we do a DELETE the deleted table represents what got deleted and if we do an UPDATE, we don't have an updated one. Wat we really have is the inserted table. It's the changes that were made. So if I want to say output some information about the roq that's just getting updated, I could say OUTPUT inserted.Name. So hit that Execute and we find that we have just updated ProductCategoryID number 57 with a ParentID of 1 where the name was Custom Bikes and we are able to get that information out about what we just updated.

Nine times out of ten, the real use for the OUTPUT clause is going to be after an INSERT. That's the most important thing for most application developers is allow them to insert a new row and find out immediately what the identity or the guid of that row was, but it can also be used with your UPDATE and with your DELETE.

Find answers to the most frequently asked questions about SQL Server 2008 Essential Training.


Expand all | Collapse all
please wait ...
Q: I'm having problems installing the free Express R2 version of SQL Server on Windows XP. I tried 64-bit and 32-bit versions. In the videos, the author installs from a DVD. Do I need to do the same?
A: While the author installs from a DVD, it's not strictly necessary. There certainly shouldn't be a problem installing the Express edition from a regular download. That's the way it's intended to be installed.

If you're using Windows XP, the only officially supported version is the 32-bit version. However, you do need to make sure that your Windows XP install is completely up-to-date and patched, with XP Service Pack 3 installed. (See http://msdn.microsoft.com/en-us/library/ms143506.aspx#Express32 for formal requirements.)

It's not unusual for the install process to take a while, and with older operating systems like XP, you'll often have to back it out and try again, as usually there's a bunch of prerequisites that need to be installed. (Like the .NET Framework 3.5 SP1, the correct version of Windows Installer, etc.)
Q: The link to the installer for the AdventureWorks sample database, as shown in the Chapter 2 movie "Installing sample databases," no longer works. Where can I find the installer?
A: Microsoft has reorganized its site. The sample files are still there, but they're a bit harder to find. To install them:

1) Visit http://msftdbprodsamples.codeplex.com/.
2) Click the link to "SQL Server 2008 R2 OLTP."
3) Click the AdventureWOkrs2008R2 Data File link and agree to the conditions to download the MDF file.
4) Move the MDF file to your SQL Server Directory, usually located at C:\Program Files\Microsfot SQL Server\MSSQL 10_50.MSSQLSERVER\MSSQL\DATA.
5) Open the SQL Sever Management Studio and connect to your instance using an account with administrative privileges.
6) Attach the sample database by right-clicking the Databases folder in the Object Explorer and choosing Attach from the pop-up menu.
7) Click the Add button in the next menu and navigate to the MDF file in the Locate Database Files window that appears. Select it and click OK.
8) Remove the reference to the log file in the "AdventureWorks2008R2" database details: pane by selecting the Log entry and clicking removing.*
9) Click OK to return to SQL Server Management Studio and complete the attachment process.

*MDF files are the "data" files for SQL Server databases. They often come along with LOG files (ldf files). This one didn't so we need to REMOVE the reference to the non-existent log file. Select the second row in the lower section (it should say File Type: Log and Message: Not Found) and click the REMOVE button.

For an illustrated version of these instructions (with screenshots), click here for a PDF version.
 
Share a link to this course

What are exercise files?

Exercise files are the same files the author uses in the course. Save time by downloading the author's files instead of setting up your own files, and learn by following along with the instructor.

Can I take this course without the exercise files?

Yes! If you decide you would like the exercise files later, you can upgrade to a premium account any time.

Become a member Download sample files See plans and pricing

Please wait... please wait ...
Upgrade to get access to exercise files.

Exercise files video

How to use exercise files.

Learn by watching, listening, and doing, Exercise files are the same files the author uses in the course, so you can download them and follow along Premium memberships include access to all exercise files in the library.
Upgrade now


Exercise files

Exercise files video

How to use exercise files.

For additional information on downloading and using exercise files, watch our instructional video or read the instructions in the FAQ.

This course includes free exercise files, so you can practice while you watch the course. To access all the exercise files in our library, become a Premium Member.

join now Upgrade now

Are you sure you want to mark all the videos in this course as unwatched?

This will not affect your course history, your reports, or your certificates of completion for this course.


Mark all as unwatched Cancel

Congratulations

You have completed SQL Server 2008 Essential Training.

Return to your organization's learning portal to continue training, or close this page.


OK
Become a member to add this course to a playlist

Join today and get unlimited access to the entire library of video courses—and create as many playlists as you like.

Get started

Already a member?

Become a member to like this course.

Join today and get unlimited access to the entire library of video courses.

Get started

Already a member?

Exercise files

Learn by watching, listening, and doing! Exercise files are the same files the author uses in the course, so you can download them and follow along. Exercise files are available with all Premium memberships. Learn more

Get started

Already a Premium member?

Exercise files video

How to use exercise files.

Ask a question

Thanks for contacting us.
You’ll hear from our Customer Service team within 24 hours.

Please enter the text shown below:

The classic layout automatically defaults to the latest Flash Player.

To choose a different player, hold the cursor over your name at the top right of any lynda.com page and choose Site preferencesfrom the dropdown menu.

Continue to classic layout Stay on new layout
Exercise files

Access exercise files from a button right under the course name.

Mark videos as unwatched

Remove icons showing you already watched videos if you want to start over.

Control your viewing experience

Make the video wide, narrow, full-screen, or pop the player out of the page into its own window.

Interactive transcripts

Click on text in the transcript to jump to that spot in the video. As the video plays, the relevant spot in the transcript will be highlighted.

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.