Miles Neale (9/5/2012)

---

... Best read and understand parts of TAOCP vols 4 and 5 to get background and then find other particulars unique to the challenge you are faced...

Sean Lange (9/5/2012)

---

RBarryYoung (9/5/2012)

---

Hmm, I just noticed what this is trying to do (thanks, Lowell!).

Why on earth would you even want to do this? If a #temp still exists,...

Note: 4-year old thread.

Jeff Moden (9/4/2012)

---

RBarryYoung (9/4/2012)

---

Jason-299789 (9/4/2012)

---

Jeff Moden (9/3/2012)

---

In SQL Server, that's a pretty insane requirement because that would make a character based date....

Hmm, I just noticed what this is trying to do (thanks, Lowell!).

Why on earth would you even want to do this? If a #temp still exists, it's because someone...

Duplicate post. Please do NOT cross-post.

Luis Cazares (9/5/2012)

---

Are you doing that in a Stored Procedure? It might not work since it will verify that all the code is correct to compile it. I might be...

And make them do their rollout/upgrade changes on a test or backup copy of your database first. Only when that suceeds should you consider giving them (temporary) access to...

The facility that does this is called "SQLMail", here's the msdn article on how to get started with it: http://msdn.microsoft.com/en-us/library/aa213788(v=SQL.80).aspx.

However, be forewarned: SQLMail requires you to install the Outlook client...

Well, I'm no fan of cursors, but the error says it all: The number of variables in the INTO clause of your FETCH commands must match the number of...

Jason-299789 (9/4/2012)

---

Jeff Moden (9/3/2012)

---

In SQL Server, that's a pretty insane requirement because that would make a character based date. Since you're...

Some points:

1. A recursive CTE is likely to be slower, not faster.

2. It really is not at all clear what you are trying to do here. You may want...

Is CrossDB chaining set on both databases? Or is it set for the whole Sever?

And are you still getting the same error?

kumar-378458 (9/4/2012)

---

Hi RBarryYoung,

As you suggested I tried with Cross-db changing setup. But no luck. I got the same error. Can you please explain step by step code to do this...

First, stop trying to use the EXECUTE AS statement. Instead you should be using the EXECUTE AS clause of the CREATE TRIGGER statement.

Secondly, the login that you are using...