This is the way databases work. I'm guessing you (like I) come from a
desktop database background where the system will lock a record for editing.
Not so for SQL servers.
One strategy you can use is to add a lock field to your record.
Then, before you commit your change (issue the UPDATE stateme
On Tue, Nov 13, 2001 at 10:28:53PM -0700, Karl J. Stubsjoen wrote:
> Hello,
>
> I have a fairly active and large DB. I need to create a new index
> on a column. It will take (just guessing) 15-30 minutes for the
> entire creation. I've got different people hittiing this table all
> the time, m
The table not locke error occures when you have issued a lock tables
command, and then access a table not included in the lock tables call.
You must lock all tables you intend to access between the lock and
unlock calls.
Werner Stuerenburg wrote:
> As I said earlier, I have troubles with 3 ta
