Skip to content

shannonlowder.com

Menu
  • About
  • Biml Interrogator Demo
  • Latest Posts
Menu

SQL 101 – TRANSACTION

Posted on March 1, 2006February 9, 2011 by slowder

As I mentioned in my previous post, before you move on to more difficult topics I need to share with you what a TRANSACTION is, and how to use them.  By now I’m sure you’ve seen t-SQL on tutorials.  The T stands for transactional.  If you don’t know what a TRANSACTION is, that’s pretty meaningless, right?

Well every action you do in SQL can be a unit.  If you use the command

BEGIN TRANSACTION

Before each of these units, you have the ability to decide whether or not to keep the changes you make after that point.  Without declaring BEGIN, you can’t tell the server  “oops, I made a mistake!  I’d like to take a mulligan on that one.”  The server just does what you tell it to do.  But with a transaction, you can make unit changes, and decide after the change if you want to keep it or not.  Let’s look at some examples, grab this file if you’d like to follow along on your own server.

BEGIN TRANSACTION

INSERT INTO productSale
SELECT 'Shannon Lowder', 'paper', '1/1/2000', 5, 1.00 UNION
SELECT 'Shannon Lowder', 'pencil', '1/1/2000', 10, 1.00 UNION
SELECT 'Shannon Lowder', 'pen', '1/1/2000', 20, 1.00 UNION
SELECT 'Shannon Lowder', 'paper', '1/1/2050', 200, 1.00

SELECT *
FROM productSale
/*
--the result:
buyer    productName    purchaseDate    qtypurchased    pricePaid
Shannon Lowder    paper    2000-01-01 00:00:00.000    5    1.00
Shannon Lowder    paper    2050-01-01 00:00:00.000    200    1.00
Shannon Lowder    pen    2000-01-01 00:00:00.000    20    1.00
Shannon Lowder    pencil    2000-01-01 00:00:00.000    10    1.00
*/
ROLLBACK TRANSACTION

SELECT *
FROM productSale
/*
--the result
buyer    productName    purchaseDate    qtypurchased    pricePaid
*/

In this example, I decided the records I inserted were wrong, and I wanted to undo those changes.  By calling ROLLBACK TRANSACTION, the server basically does a CTRL+z for me, and undoes the change.

But, if i wanted to keep those records I would do the following, instead.

BEGIN TRANSACTION

INSERT INTO productSale
SELECT 'Shannon Lowder', 'paper', '1/1/2000', 5, 1.00 UNION
SELECT 'Shannon Lowder', 'pencil', '1/1/2000', 10, 1.00 UNION
SELECT 'Shannon Lowder', 'pen', '1/1/2000', 20, 1.00 UNION
SELECT 'Shannon Lowder', 'paper', '1/1/2050', 200, 1.00

SELECT *
FROM productSale

COMMIT TRANSACTION

SELECT *
FROM productSale

This time the records remained.  Both of these examples are very simple.  I just want you to learn the ideas behind the TRANSACTION.  By using them, you can handle errors and leave your server in a safe state.  You can control how the error leaves your tables, since you can have an all or nothing result.  That way if all the changes aren’t successful, then none of the changes will stick.  It makes things much nicer, especially when dealing with large loads, or large changes to your database.

Do you have any questions?  If so, please send them in.  I’m here to help!

Previous: UPDATE Next: DELETE

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • A New File Interrogator
  • Using Generative AI in Data Engineering
  • Getting started with Microsoft Fabric
  • Docker-based Spark
  • Network Infrastructure Updates

Recent Comments

  1. slowder on Data Engineering for Databricks
  2. Alex Ott on Data Engineering for Databricks

Archives

  • July 2023
  • June 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • October 2018
  • August 2018
  • May 2018
  • February 2018
  • January 2018
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • June 2017
  • March 2017
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • August 2013
  • July 2013
  • June 2013
  • February 2013
  • January 2013
  • August 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • March 2005
  • February 2005
  • January 2005
  • November 2004
  • September 2004
  • August 2004
  • July 2004
  • April 2004
  • March 2004
  • June 2002

Categories

  • Career Development
  • Data Engineering
  • Data Science
  • Infrastructure
  • Microsoft SQL
  • Modern Data Estate
  • Personal
  • Random Technology
  • uncategorized
© 2025 shannonlowder.com | Powered by Minimalist Blog WordPress Theme