Thanks guys!

Well, don't have a good answer, but perhaps your observation about the failure always occurring on the last server

processed (i.e., your server #4) is significant.

Try changing the order of the...

Like the other poster said, what happens when you try sending a test email?

If you try something like this:

EXEC msdb.dbo.sp_send_dbmail

@profile_name = 'DBMailPublicProfile', --...

[font="Courier New"]

If what they're saying is true, the 4 coordinates are simply:

(MINX, MAXY) ------------ (MAXX, MAXY) ...

Like one of the other poster says, try using a stored proc.

You can use the OPENROWSET approach to create (in-effect) an on-the-fly linked server for each server connection.

And then UNION...

Don't really know why you're getting the error, but it looks like the problem comes into play when you try to go against all 1.5 million rows in the table with...

Shrikant,

Thanks!  Knew it had to be there somewhere...

- john

Can you please list the definition for the "T1" table.

My suggestion is simple:

Try the upgrade in a test environment first, and see what happens.

There is a SQL 2005 upgrade wizard that runs, and will produce a nice report of any compatibility...

Hey, thanks for replying.  Yes--you're right!

Sorry, I didn't notice they were using the "sp_executesql" which adds an additional level of quotes.  I had just cut/extracted the body of the...

OK, thanks for the suggestions all.

- john

trigger and have some job/service check for new adresses every minute and process them there.

I second Remi's proposed...

Yes.  Nice work, and thanks!

Disagree.  Although in general you're right about the ";" terminating the command, here if it ended the statement, then there wouldn't be any parameters passed to the proc!  Note that the...

Yes. 

At least answer (c) appears to be what I get when I run the command on my SQL 2000 box here. 

Still not exactly sure why the ";" doesn't cause trouble -- it appears...