In this case it is an error... a serious one.

One year ago when the databases where created some tables add NEWID() for the GUID columns.

Our clients used the applications and insert data, modify, what ever...

The scripts were corrected and putted static GUIDs a few months ago.

Every month there are upgrades: we compare the last month "base" scripts with this month and create the upgrade script.

Some upgrade scripts have data updates compared by the GUID column.

In old databases the GUID may be different so no row will be updated and we don't want that to happen. An error must be raised and we will modify the script so it will, by some other column or what ever it may be needed, modify the desired row.

Since the upgrade software is in C# I'll probably use the InfoMessageEvent to catch the "silent" output from SQL Server (the messages) and see if there's any 0 rows affected message.

Thanks,

Pedro