May well not apply in your case, but it may be possible to set an additional flag on each record that says if it is to be considered or not.

Hi Eric and Thomas

It's a matter of timing.

In the application as it stands, the ResendLimit says the max times the relevant communication can be resent -...

To expand on Jeff's comment, the following shows information that is available
BEGIN TRY
-- Generate a divide-by-zero error.
SELECT 1/0;
END TRY
BEGIN CATCH...

Thanks Jeff.

Wow, nearly 1,000,000 points. I am in awe.  Just as well SQLServerCentral didn't use even a smallint for that (and they should watch out if it is...

Thanks srienstr.
That was the main option I considered (along with casting within the subtraction).
I eventually decided against it - less on the overhead grounds - more because I...

db_send_dbmail returns a mailitem_id immediately (the email is queued to be sent later). Use that to read msdb.dbo.sysmail_mailitems and check sent_status at a later time (values 0-3 in my...

For me (with 2008 R2) it queues the message (and this makes logical sense to me).

Anyway, when you call send_dbMail, if it all is basically OK you get...

A simple way to get around the issue of modified_on and modified_by causing records to expand is
a) Use an ID for people (e.g. an int) so it is always...

Perhaps I'm misunderstanding how I should use the variant of the function you suggest.

Here is an example of how I would expect my version to be used, in...

I'm not sure what you'd expect the function to return when the number is not a divisor of the number of units in the implied containing period.

For example,...

Considering the underlying problem - how do we get the integer value nearest to 0  - I would use cast.
select cast(123.45 as int), cast(-123.45 as int), cast(123.89 as int),...

If the tables have multiple columns and you want to count where all columns match

select count(*) from (
select * from dbo.c_scope
intersect
select *...

I also use Netezza. There are some areas where it is much more user-friendly, for example:

1. In a query use alias names you just created. Example:...

You need to start with a sound design, thinking through the possible issues, then implement it.

The first design, with a suffixed number, is basically fine in principle. It will...

The use of Upper comes from an implementation of this on a different database that is case sensitive (Netezza) and a bit of (buggy) transcription. Whilst of course the...