That's maybe the difference - I want to use the same disks as the first instance on SQLCluster1 is using?

But I don't see which option on the install screen allows me to do this?

I don't want to install a new SQL Cluster name with a named instance but a...

I thought so too but the documentation I have read doesn't seem to allow it. Do you have a link?

The -o / -r switched gave different levels of detail. The output from running manually in SSMS was different again.

Yes it was 3 hours ago.

Sorry yes I am connected to master when I execute this code.

I also checked the AUTO_UPDATE_STATISTICS_ASYNC option and it was already set to OFF anyway.

I still don't understand how another...

Yes I'm connected to DB1, but I'll take a look at your option.

BTW, this works fine in SSMS, it's only when the code is run from a SQL job step??

thanks for the explanation. so if the proc owner is different from the table owner for example then the caller will have to have SELECT permissions on the underlying table?

Yes I thought so - just having some issues with a spreadsheet accessing the data but I think it's the connectionstring that is incorrect.

Something like:

USE DBName

GO

BEGIN TRY

SET NOCOUNT ON

DECLARE @ErrorMessage NVARCHAR(300)

--XXXXXX---------------------------------------------------------------------

IF EXISTS (SELECT * FROM sys.database_principals WHERE name = N'UserName')

DROP USER [UserName]

IF NOT EXISTS (SELECT * FROM sys.database_principals WHERE name = N'UserName')

BEGIN

CREATE...

I know this is quite an old message, but does UCP actually collect the same information as Data Collector, but UCP now supersedes it? As it looks like you can't...

Thanks some good info there. I did get it working using:

SET @DynamicSQL = @LinkedServerREP + '.<DBName2>.dbo.sp_executesql '

SET @sql = N'DROP TABLE ' + @TableName + ''

EXECUTE @DynamicSQL

One final issue. I'm trying to dynamically build the execute_sql part:

SET @DynamicSQL = @LinkedServerREP + '.<DBName>.dbo.sp_executesql '

SET @sql = 'N''DROP TABLE ' + @TableName + ''''

--PRINT

Thanks for the confirmation.I ended up creating linked server on the destination server back to the source and executing this:

SELECT * INTO DBName.dbo.' + @TableName + ' FROM ' +...

Oh hang on i see what you mean.