Database

PIEBALDconsult wrote:

If you use stored procedures (and you shouldn't),

When I implement a system like that, sending email or whatever, I put a Status field in the table to indicate ( 0=New , 1=Sending , 2=Sent ). When I select the New rows, I also set the Status to Sending, then when I'm done I set the Sending rows to Sent.

"UPDATE Email SET Status=1 WHERE Status=0 ; SELECT * FROM Email WHERE Status=1"

Send the emails.

"UPDATE Email SET Status=2 WHERE Status=1"

jrahma wrote:

using sql_reader1

PIEBALDconsult wrote:

I generally write Windows Services that cycle every ten to fifteen seconds

Mycroft Holmes wrote:

grids

Mycroft Holmes wrote:

(relearning) Oracle.

PIEBALDconsult wrote:

I have never understood the reason so many devs use the DataAdapter and load a whole butt-load of data at once when they don't use it all at once.

using (var ad = new SqlDataAdapter("sp_send_pending_sms", ConfigurationManager.ConnectionStrings["SQLdb"].ConnectionString))
{
    ad.SelectCommand.CommandType = CommandType.StoredProcedure;
    var dt = new DataTable();
    ad.Fill(dt);

    // blah blah blah. do your work.
    ad.AcceptChangesDuringUpdate = true;
    ad.Update(dt);
}

GamleKoder wrote:

is only for selecting (reading) data.

Spectre_001 wrote:

You can not update through a DataReader