But I do not see it explain how do do that with SQL express I guess?
Anyone have those directions?
Well, I have, of course. ![smiley smiley](https://www-secure.symantec.com/connect/sites/default/modules/contrib/ckeditor/ckeditor/plugins/smiley/images/regular_smile.png)
What the support engineer did was:
- connect to the BEDB database with SQL Server Management Studio
- list the content of the table:
SELECT * FROM CatImageFileDeleteTable
- check the values in the Location column against the filesystem to make sure none of those paths did actually exist
- being assured of that, he delete the entries individually:
delete from CatImagefileDeleteTable where Location = 'G:\BEData\IMG000181'
delete from CatImagefileDeleteTable where Location = 'G:\BEData\IMG000246'
delete from CatImagefileDeleteTable where Location = 'G:\BEData\IMG000310'
- Finally he had me check a few days later whether the table was still empty. It was.
Of course that process could be streamlined a bit, but the engineer was obviously reluctant to summarily delete any entries from that table whose corresponding paths might still exist in the filesystem. He did not explain what evil consequences that might have.
Meanwhile, the root cause of the problem (infinitely retrying a removal that failed because the object was already gone) remains, for all that I know, unfixed.