Sean Lange (5/2/2012)

---

sheesh in looking at my post I could have...

Yes, the import/export tool will automtically copy schema names over if it doesn't find them. That's by design.

I'd expect a statement complete event at the end of it, unless you've filtered the trace somehow.

Try this:

SELECT Matters.FeeEarnerRef,

Entities.Code,

Matters.Number,

Entities.Name,

...

Figured as much.

Does the reason and solution make sense?

That error message almost always means you're trying to pass Windows credentials more than one "hop". Search online for "Kerberos double-hop" and you'll find the details on what that...

I keep a log of all DDL changes to all my databases, and I get that kind of information from there. Source control works as well if not better....

Exact reason for the problem and solution to it posted on the other copy of this thread.

Too...

What you need is something comparable to this:

IF OBJECT_ID(N'tempdb..#SCRAMBLE') IS NOT NULL

DROP TABLE #SCRAMBLE ;

CREATE TABLE #SCRAMBLE

(FNAME VARCHAR(10),

...

Ignoring the infinite loop about where to post.

Your update statement doesn't specify which row in Scramble matches which row in your random select.

SQL Kiwi (5/2/2012)

---

GSquared (5/2/2012)

---

The parentheses on Top are only needed outside of Select statements, but whatever is wanted on the standards for that. That's style, not function, so whatever...

Something like this?

IF OBJECT_ID(N'tempdb..#mytable') IS NOT NULL

DROP TABLE #mytable ;

CREATE TABLE #mytable

(event INT,

event_date DATE)

INSERT #mytable

VALUES...

Honestly, all I can say for sure is that it looks massively over-complicated for a standard purge process, and that I'd have to work with it in your data to...

RobertYoung (5/2/2012)

---

I guess you not noticed the harlot hussy...