AUFK table update performance ** RESOLVED **
Put the same WHERE clause in your UPDATE statement.
Thanks Guest but you DONT need to specify the same where clause, the work area already contains the primary key for the update.
Are you issuing a COMMIT WORK after your update?
Yorkie
Thanks Yorkie but the problem is the time taken to do the update, not what happens afterwards.
The problem has now been resolved by changing some basis system settings..
Dave.
The table was being affected by a stored procedure placed on it by a consultancy some time ago, I analysed the procedure and found that it could be removed without problem, this has been done and the code performs just fine, thanks.
Dave W.
What's a "stored procedure"? How can you check if one has been attached to a table? Thks.
The table was being affected by a stored procedure placed on it
Dave W.
Did you not mean actually a 'trigger' ?
No Guest13, I meant a stored procedure.
" A trigger is a condition, which if true, causes a stored procedure to execute. Stored procedures are SQL code embedded in the database that provides critical information to the end user when triggered ".
DW