Click here to Skip to main content
14,539,384 members

Sending a DataTable to a Stored Procedure

Rate this:
4.75 (50 votes)
Please Sign up or sign in to vote.
4.75 (50 votes)
10 Jul 2012CPOL
Sending a DataTable to a Stored Procedure using Table Valued Parameters.


This is a small article explaining how to send an entire data-table to a Stored Procedure in the database server as an input parameter. 


It uses a logic which allows us to do add, modify, and delete operations on a set of records in the database using a simple form. The details also need to be shown after adding, updating, and deleting of records in a table. And the data-table should be given to a stored procedure to perform the operations. This feature will work with SQL Server 2008.


  1. For each event on the page the form will not be interacting with the database. This reduces server round trips. 
  2. All necessary operations such as:
    1. Inserting a new record
    2. Updating an existing record
    3. Deleting an existing record

    are performed on client side only. They will be persisted in the database only after getting confirmation from the user. So, the performance of the application will improve.

  3. After performing a certain action (such as Insert, Update, or Delete) on the grid-view the data will be saved in “Session”. And whenever the data is required, it is be fetched from the Session. 
  4. We send the entire data-table from the session to the database for manipulation, and with the use of a Stored Procedure we can do operations such as insert, delete, and update.
  5. It is easier to perform all operations on a set of rows at a time.
  6. The user can deal with thousands of data-rows at the same time without a connection.
  7. Extends the functionality of programming in a database engine.

Using the code

When a page is getting loaded the first time, data from the database is loaded to a data-table. In that data-table a column is added (named Operation). Whenever the user performs an action on the grid-view, the indicator bit is added to that column for that record (Insert 0, Update 1, and Delete 2). If the user clicks on a delete link on a particular row then the operation column of that row is updated to 2, and in the RowDataBound event of the grid-view we hide the records whose operation bit is 2. The temporary table is stored in session state. Before performing any operation, the session table will be called and the action will be performed on that table and again that table will be stored in the session. After performing all the necessary operations, when the user clicks on the Save button, the function fnMangeOperations is called which will filter all the rows on which the operation was performed and the Save button will send only those details in which the operation has to be performed (you can find the function fnMangeOperations in the source code from the attached files). 

Step 1: Declaring global variables:  

private clsEmpDetails _objEmpDetails;
private DataTable _dtEmpDetails;
private DataTable _dtEmpDetailsVals;

Step 2: Initializing the data members when page loads.

protected void Page_Load(object sender, EventArgs e)
    if (!IsPostBack)
        _objEmpDetails = new clsEmpDetails();
        _dtEmpDetails = _objEmpDetails.fnGetDetails();
        if(_dtEmpDetails != null){
           //Adding a new column to the table which will store the operation details
           //For new insert it will store 1
           //For updating the existing record it will store 0
           _dtEmpDetails.Columns.Add("Operation", typeof(string));
           Session["EmpDetails"] = _dtEmpDetails;
           gvEmpDetails.DataSource = _dtEmpDetails;

Just store the data in session and maintain the indicator for each operation. The operation will be like this:

protected void gvEmpDetails_RowCommand(object sender, GridViewCommandEventArgs e)
    if (e.CommandName == "AddNew") 
            _dtEmpDetails = Session["EmpDetails"] as DataTable;
            string strID = (TextBox)gvEmpDetails.FooterRow.Cells[0].FindControl("txtInsID")).Text;
            string strName = (TextBox)gvEmpDetails.FooterRow.Cells[1].FindControl("txtInsName")).Text;
            string strAddress = (TextBox)gvEmpDetails.FooterRow.Cells[1].FindControl("txtInsAddress")).Text;
            _dtEmpDetails.Rows.Add(strID, strName, strAddress, "0");
            Session["EmpDetails"] = _dtEmpDetails;
            fnBindEmpDetails(); //This function will bind the data to the gridview by fetching the data from session
        catch(Exception ex){            
             //Handle your exception

On click of the Save button, call the following function by passing your DataTable as a parameter.

public string fnStoredProc(DataTable dtDetails)
    string strMsg = "";
        fnConOpen();//Function for opening connection
        SqlCommand cmdProc = new SqlCommand("spEmpDetails", con);
        cmdProc.CommandType = CommandType.StoredProcedure;
        cmdProc.Parameters.AddWithValue("@Type", "InsertDetails");
        cmdProc.Parameters.AddWithValue("@Details", dtDetails);
        strMsg = "Saved successfully.";
    catch (SqlException e) {
        //strMsg = "Data not saved successfully.";
        strMsg = e.Message.ToString();
        fnConClose();//Function for closing connection

    return strMsg;

Procedure structure

First create a table type with matching columns which comes from the front-end. In this case:

/*Creating type for the procedure parameter*/
    ID INT, Name VARCHAR(3000), Address VARCHAR(8000), Operation SMALLINT

Write the procedure for the operations.

@Type VARCHAR(15),
@Details EmpType READONLY
        SELECT * FROM EmployeeDetails
            --For deleting the details from the table
            DELETE FROM EmployeeDetails WHERE ID IN(SELECT ID FROM @Details WHERE Operation=2)
            --For updating the details in the table
            UPDATE e SET e.Name=d.Name, e.Address=d.Address FROM EmployeeDetails e, @Details d 
            WHERE d.ID=e.ID and d.Operation=1
            --For inserting the new records in the table
            INSERT INTO EmployeeDetails(ID, Name, Address) 
            SELECT ID, Name, Address FROM @Details WHERE Operation=0;

Note: This procedure takes a datatabe as its parameter and performs insert, update, and delete operations based on the table data.

End point

Thank you for reading this article. Any suggestions will be appreciated.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Software Developer (Senior)
Malaysia Malaysia
I've been working with various Microsoft Technologies. I have earned my Microsoft Certified Technology Specialist (MCTS) certification. I'm a highly motivated self-starter with an attitude for learning new skills and utilizing that in my work.

--Amit Kumar
You can reach me at:
Facebook | Linkedin | Twitter | Google+

Comments and Discussions

AnswerRe: addnew button Pin
_Amy4-Jul-12 5:21
professional_Amy4-Jul-12 5:21 
GeneralRe: addnew button Pin
KP Lee4-Jul-12 20:58
MemberKP Lee4-Jul-12 20:58 
GeneralRe: addnew button Pin
_Amy4-Jul-12 23:01
professional_Amy4-Jul-12 23:01 
SuggestionSQL 2008 and later only Pin
Drew Rhoades3-Jul-12 8:46
MemberDrew Rhoades3-Jul-12 8:46 
GeneralRe: SQL 2008 and later only Pin
_Amy3-Jul-12 17:46
professional_Amy3-Jul-12 17:46 
QuestionWhat about concurrency? Pin
Jaime Premy3-Jul-12 5:55
professionalJaime Premy3-Jul-12 5:55 
AnswerRe: What about concurrency? Pin
_Amy3-Jul-12 6:25
professional_Amy3-Jul-12 6:25 
GeneralRe: What about concurrency? Pin
Jaime Premy5-Jul-12 4:06
professionalJaime Premy5-Jul-12 4:06 
Well that's exactly the problem, I think, cause let's say Bob loads a table and updates record 10 then takes a coffee break, and Jenn happens to load the same table, update the same record and save the table back, while bob is still sipping his coffee, I think Jenny will be in for a surprise after Bob saves back his copy of the table, don't you think???

What if they update/delete identical multiple records?
What happens with autoid inserts from both Jenn and Bob? If the autoid is a pk to a column in another table, this will surely create some key constraint problems.

I guess that these problems may also arise in a normal "instant" Insert/Update/Delete scenario, in the very unlikely case of 2 or more operations occuring at the exact same millisecond, but even then this would hardly affect more than 1 record.
GeneralRe: What about concurrency? Pin
KP Lee3-Jul-12 19:22
MemberKP Lee3-Jul-12 19:22 
QuestionEntity Framework Pin
Brian Savoie2-Jul-12 18:54
MemberBrian Savoie2-Jul-12 18:54 
GeneralRe: Entity Framework Pin
_Amy2-Jul-12 19:03
professional_Amy2-Jul-12 19:03 
GeneralRe: Entity Framework Pin
Marbry Hardin5-Jul-12 12:33
MemberMarbry Hardin5-Jul-12 12:33 
GeneralMy vote of 5 Pin
wiredeye2-Jul-12 7:40
Memberwiredeye2-Jul-12 7:40 
GeneralRe: My vote of 5 Pin
_Amy2-Jul-12 7:52
professional_Amy2-Jul-12 7:52 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Posted 29 Jun 2012

Tagged as


104 bookmarked