hmm...why not run a profiler trace to see the code causing this? From this you could understand whether its a trigger or procedure or adhoc query. You should fix it at the source rather than doing clean up and recycle at table
If they had a DBA, the problem would not occur in the first place, right?
N 56°04'39.26" E 12°55'05.63"
Hmm..How can that be guaranteed? How will a DBA be aware of all internal logic used by the application and causing the creation of this anonymous row? That might be something related to business logic not implemented in right way.