> A transactions is exactly like the original poster stated it. > > Assuming all Update, Select, Insert Commands are Atomic. A transaction > allows the user to group a bunch of commands together and state they should > be considered atomic, whereas if there is "a failure", then none of them are > committed. > > The confusion lies in the scope that "A Failure" is defined. IE in the > Database Engine, or in the Application using the database engine.
The transaction doesn't seem any different than a snapshot of the database that you can restore to. I just wondered why there were two methods of doing the same thing.
