Adam wrote:

> It is a regular operation, potentially every couple of minutes. A
> service is run that makes some changes to the table (a mini
> replication if you like). Triggers then store a notification record in
> the table. If the application does not check its notifications for a
> while, there may be many notifications for the same record (which has
> changed many times in the interim).
>
> Of course a distinct is used in the query to retrieve the records, but
> I don't like the idea of letting it go, particularly if the
> application is shut down for an extended period of time (someone goes
> on holidays for example).

Do you actually need to delete all duplicates and insert a new one?
Wouldn't it be sufficient to delete all of the duplicates except one?

Kjell
--
--------------------------------------
Kjell Rilbe
Adressmarknaden AM AB
E-post: kjell.rilbe@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64