chris.johnson 46127 (2/12/2013)

---

To execute the code against a different database then you just need to put the database name infront of the sp_ExecuteSQL stored proc. So:

EXEC DatabaseName.dbo.sp_ExecuteSQL

I think if you...

Called sp_ExecuteSQL as a 3 part name works brilliantly, however it won't recognise that I have set QUOTED_IDENTIFIER and ANSI_NULLS to on earlier in the procedure.

Much closer though, thank you...

Sorry, last post was a bit vague. This one may or may not help 😀

I know this code doesn't work, but this is the kind of thing I'm trying to...

Thank you both for your responses.

The reason why the parameters are there is because of the second part of the problem, this code must be executed against a different database...

Do you have a description of the error?

Unless I'm going mad, you have more columns in the second SELECT than you do in the first. Statements in a Union must have the same number of columns.

Nevermind, turns out I'm over complicating matters 🙂

For anyone who comes across this problem themselves, the problem seemed seemed to stem from the DB Schema that the reference table belonged to.

The table was in a user defined...

So this error turned out to be a problem with the amount of columns being used in the Fuzzy Lookup. It seems there is a limit of 10 columns that...

Still struggling with this if anyone has any suggestions.

Wonderful, thanks for your response.