Re: trace uncommitted inserts

From: Mladen Gogala <>
Date: Fri, 29 Apr 2011 16:30:35 +0000 (UTC)
Message-ID: <>

On Thu, 28 Apr 2011 13:08:02 -0700, Tiago wrote:

> I have an application written in .net, I have only the .exe, not the
> source. It keeps processing data from an external source and inserting
> on a table, but sometimes I can't see the data on the table. Sometimes
> it inserts, sometimes doesn't. Vendor is taking too long to figure that
> out, since the message that get inserted look like exactly like the one
> that doesn't :( I suspect it is trying to commit but something wrong
> happens. App log doesn't show any error, external data source says it
> sent the data correctly, App log says it received, but nothing is
> inserted.

Now this looks like an intelligent design! There are entities called "triggers" which can be made to fire on insert. Also, the vendor looks like a very competent application producer. Can you reveal us the name of that brilliantly competent software company? The other users need to be warned.

Received on Fri Apr 29 2011 - 11:30:35 CDT

Original text of this message