Note that there are some explanatory texts on larger screens.

plurals
  1. POSituations in which a DELETE statement does not execute
    primarykey
    data
    text
    <p>I have an ERP system which I'm trying to debug and at some point when issuing a command from frontend a set of queries is executed in SQL Server.</p> <p>In the set of queries there is a <code>DELETE</code> statement that should execute and remove some records from a table, but for some reason those records are not removed.</p> <p>I have tried a few situations to figure out why this doesn't happen.</p> <ol> <li>I've tried locking the table with a large query issued both from a frontend command and from an explicit backend set of queries from SQL Server.</li> <li>I've tried to review user access to the table and that is correct.</li> <li>I've also taken into account problems with the network connection, but because there are more statements from the same set that have executed before/after this <code>DELETE</code> statement, I've kind of ruled this out. </li> </ol> <p>Is there anything else I could look at, or if you know of any possibility in which a <code>DELETE</code> statement does not execute?</p> <p>Any suggestion is helpful as I am trying to replicate the issue and I'm out of ideas. </p> <p><strong>UPDATE:</strong></p> <p>As per your request, this is the query</p> <pre><code>DELETE FROM Payments WHERE transactionID = 5005281 </code></pre> <p><strong>UPDATE 2</strong>:</p> <p>I've ran profiler when issuing the command from frontend so if a <code>DELETE</code> statement is present in the queries, then it was not supresed by application logic. Also, there are no calls to stored procedures to suspect the record is begin reinserted after DELETE.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload