Sounds about right. Just to be safe try all 3-4 options for the login type. That's how we actually found the "fix".

staindromeo1 (6/27/2011)

---

I created a column with the value types & put a bunch of if statements to perform the function with an Inner join in there. That worked for me....

Just to be 100% safe that you were not going to edit all the procs that take that...

Usually test server have much slower disks. This MAY help a little bit.

http://www.sqlskills.com/blogs/kimberly/post/instant-initialization-what-why-and-how.aspx

Just to be clear. You fixed the query that fills the parameter right? Not the proc itself?

... forgot the pivot :

SELECT

tblName--, RID

, MAX(CASE WHEN dtMx.Colid = 1 THEN ColName

...

avitale (6/27/2011)

---

Oh wow, so for some reason that last rep is getting a space added to the end of it. This is apparently throwing off the stored proc which somewhat...

SELECT

O.Name AS tblName

, C.Name AS ColName

-- build a matrix, needs (X,Y) position

, ( ROW_NUMBER() OVER ( PARTITION BY O.object_id ORDER...

In the linked server info, add the login admin with a blank password and see if that fixes it (took 3 hours and 4 of us on a pss call...

What do you mean by select?

So what's different between the runs?

My point was find a location where it works then change only 1 variable at a time untill it breaks.

You have a server / mdb that works. Awesome.

Only change...

Copy the code that is passed in profiler and run it in SSMS. Sometimes it just looks similar.

Check if you see any difference between that code and the code...

My first answer will solve your problem.

So the old linked server to the old location still works?

Just copy the settings to the new server. If that doesn't work try the admin trick I just told...