Thank you for the script and the link to the other thread;

I especially liked the snippet for resending failed mails that WayneS posted; good to have that in the toolbox.

ok, post coffee, with a clearer head, i found the answer.

the table sysmail_event_log, has the error description and the mailitem_id, so you can join it to failed items and see...

nice proc Gianluca; i added that to my snippets.

Jeff's right on target.

no matter what, if a message was generated by SQL(i.e. #row(s) affected or PRINT statements), you cannot read it into a variable with TSQL, whether you wanted...

here's my first guess, when covering the basics.

your server has a hyphen in it's name. that causes problems, in my experience.

i think the connection will have problems with that unless...

you won't be able to capture the messages via TSQL. the information is generated, but not capturable via...

you cannot change the datatype, but can you change the size?

for example, a 8 letter password using AES requires 40 characters to store the hashed value...

so if you cannot change...

I think the original poster is out of luck.

when you script a linked server, you get this specific comment/message, telling you that it won't script the password:

/* For security reasons...

camiloaguilar1 (10/21/2010)

---

I got that clear but I did not explain it that good, I create that table in temporal way. The goods are already with the client to so modifications...

i updated my post with a second sql, probably while you were reading the first version of the post...so the second...

camiloaguilar1 (10/21/2010)

---

Because we have a lot of order details from a sale. So for no wasting of lot of order papers we want to make 1 order from all the...

on my db with 51 databases, this gives me 26 rows: what does...

make sure you are comparing the actual execution plans, and not the estimated plans....

the estimated woudl probably be teh same on both, but the performance issue is in the actual...where...

well you didn't provide any examples of what was going wrong;

here's the data you posted in a consumable format, as well as a query that pulls the data you were...

Please don't crosspost. It just wastes people's time and fragments replies.

No replies to this thread please. Direct replies to http://www.sqlservercentral.com/Forums/Topic1008657-391-1.aspx