You could use the sp_add_job to create a job which deletes itself after running and then execute it using sp_start_job.

Just detach the database move the files and re-attach it

If the default instance collation is different this can cause issues in execution plans. As the database will be restored in the collation is was backed up in.

Try this.

SET LANGUAGE BRITISH

I know its a stupid question but have you checked the database/instance/field collations to ensure they are the same?

I have now fixed this.

The way round this is to bring down the cluster services on both nodes add the SQLArg registry entries back into both systems and bring the SQL...

The reason i am using this is because i am remotely execting stored procedures for example....

declare @servername varchar(255)

declare @cmd nvarchar(500)

set @SERVERNAME = 'SERVERNAME'

#CREATE A LINKED SERVER#

set @cmd = 'exec

I have run SQL Profiler and i cannot find any useful information. I am using windows pass through authentication for this and in this scenario it works fine for about 2...