Knowledge is no fun, unless you share it!!! :)

Showing posts with label TSQL. Show all posts
Showing posts with label TSQL. Show all posts

Friday, 6 December 2013

Transaction in SQL SERVER:


Transaction is very interesting topic, i have came across ever.It is very necessary for maintaining integrity of database.

So let’s see some interesting facts about transactions.

A transaction is a unit of work that is performed against a database. Transactions are units or sequences of work accomplished in a logical order, whether in a manual fashion by a user or automatically by some sort of a database program.
For example, if you are creating a record or updating a record or deleting a record from the table, then you are performing transaction on the table. It is important to control transactions to ensure data integrity and to handle database errors.
Practically, you will club many SQL queries into a group and you will execute all of them together as a part of a transaction.



Properties of Transactions:

Transactions have the following four standard properties, usually referred to by the acronym ACID:
Atomicity: ensures that all operations within the work unit are completed successfully; otherwise, the transaction is aborted at the point of failure, and previous operations are rolled back to their former state.
Consistency: ensures that the database properly changes states upon a successfully committed transaction.
Isolation: enables transactions to operate independently of and transparent to each other.
Durability: ensures that the result or effect of a committed transaction persists in case of a system failure.


Transaction Control:

There are following commands used to control transactions:
COMMIT: to save the changes.
ROLLBACK: to rollback the changes.
SAVEPOINT: creates points within groups of transactions in which to ROLLBACK
SET TRANSACTION: Places a name on a transaction.

Transactional control commands are only used with the DML commands INSERT, UPDATE and DELETE only. They can not be used while creating tables or dropping them because these operations are automatically committed in the database.

The COMMIT Command:

The COMMIT command is the transactional command used to save changes invoked by a transaction to the database.
The COMMIT command saves all transactions to the database since the last COMMIT or ROLLBACK command.

The syntax for COMMIT command is as follows:
COMMIT;

The ROLLBACK Command:

The ROLLBACK command is the transactional command used to undo transactions that have not already been saved to the database.
The ROLLBACK command can only be used to undo transactions since the last COMMIT or ROLLBACK command was issued.

The syntax for ROLLBACK command is as follows:
ROLLBACK;

The SAVEPOINT Command:

A SAVEPOINT is a point in a transaction when you can roll the transaction back to a certain point without rolling back the entire transaction.

The syntax for SAVEPOINT command is as follows:
SAVEPOINT SAVEPOINT_NAME;

This command serves only in the creation of a SAVEPOINT among transactional statements. The ROLLBACK command is used to undo a group of transactions.

The syntax for rolling back to a SAVEPOINT is as follows:
ROLLBACK TO SAVEPOINT_NAME;

The RELEASE SAVEPOINT Command:

The RELEASE SAVEPOINT command is used to remove a SAVEPOINT that you have created.

The syntax for RELEASE SAVEPOINT is as follows:
RELEASE SAVEPOINT SAVEPOINT_NAME;

Once a SAVEPOINT has been released, you can no longer use the ROLLBACK command to undo transactions performed since the SAVEPOINT.

The SET TRANSACTION Command:

The SET TRANSACTION command can be used to initiate a database transaction. This command is used to specify characteristics for the transaction that follows.

For example, you can specify a transaction to be read only, or read write.
The syntax for SET TRANSACTION is as follows:
SET TRANSACTION [ READ WRITE | READ ONLY ];

Your comments and suggestions are appreciated....

Thanks..!!! :)

Tuesday, 1 October 2013

Table Variables in SQL Server 2012 and differences with Temporary Tables

Table variable is handy feature of SQL Server which lets you define a variable as a table and then use it in SQL just like any other table.
Table variables were introduced in SQL Server 2000.

Temporary tables are also exists for same purpose in SQL-Server.
So there are some basic concept about usage of these two component of SQL-Server (Temporary Tables and Table Variables)

We can optimize our store procedure by repacing these components on the basis of there usages.
So today we will What is Table variables and what are the diffrence between Temporary Table and Table Variable.

SQL Server provides an variable known as table variable which is used to store data in a similar way as we store data in physical tables but with some limitations.
In SQL Server you can use temporary tables to store intermediate results. This is a common used technique to speed up query processing. Recently I came across a problem where the temporary tables were causing the performance degradation.
 
Table Variable:

You create a table variable the same way you create any other variable:
using the declare statement:

declare @TableVar table (CustomerID nchar(5) NOT NULL)

This declares a table variable named @TableVar that we can use in place of a temporary table. You can use a table variable for just about anything you'd use a regular table.
The following statements won't work however:

INSERT INTO table_variable
EXEC stored_procedure SELECT select_list INTO table_variable

We can write below piece of code inside store procedure:

DECLARE @ttable (idintIDENTITY,orderid int)
INSERT INTO @t(orderid)
SELECT a.OrderID FROM Database.TableA as a
INNER JOIN Database.TableB as b ON
a.ID = b.ID


For more diffreces you can go though the nice article written by Tejas Vashnav -
http://www.codeproject.com/Articles/415184/Table-Variable-V-S-Temporary-Table

Your suggestions is appriciated ! ! !
Next time we will learn about CTE (Common Table Expression) and it's usages.