in reply to Re: Perl DBI(ODBC) to MSSQL
in thread Perl DBI(ODBC) to MSSQL

I have multiple servers hitting the backend database. I only want one of them to make the updates to the table. I dont really care which one makes the update, just the first one to get there I guess. If I setup a transaction, will that mean that each of the servers will simply wait until the table is available and then attempt to run the code since they are doing the connections in seperate threads on seperate boxes?

Replies are listed 'Best First'.
Re^3: Perl DBI(ODBC) to MSSQL
by runrig (Abbot) on Oct 12, 2007 at 22:14 UTC
    Depending on the locking scheme for the table (page or row level or whatever else MSSQL has), you shouldn't have to wait for the table, but may have to wait for the row or page.