Has anyone come across a situation where a delete statement doesn't give an error, but also doesn't delete the rows specified?
Yes the rows exist as outside the scope of the running application, we can run the same SQL and it does delete the expected rows.
- It's sql server 2005 sp4
- It's an ad-hoc delete, i.e. not inside a transaction.
- The table is accessed via a View which just cuts down the result set on one column's content.
- The underlying table has several indexes, several foreign key parents and 2 foreign key children (both children are on delete cascade).
- There are no triggers on the table.
- The client app is connecting via odbc.
A colleague rememebers something like this in sql 2000 where deletes on tables with foreign keys had problems building an execution plan, and that just failed silently, but I can't find any details of that.
Any ideas?
Thanks
-Ade