So as you connect to SQL via SSMS as TWONODECLUSTER you put in TWONODECLUSTER in the XML file.

Remember your connecting to MSDB so you need to tell it which SQL...

Check the source where the data is coming from in the package and your transformations, if your inserting a column from the source into the identity column in the destination...

You dont provide the XML file with the cluster name you give it the virual sql cluster name which is the name that is used to connect to SQL when...

Something like the following would work

create table tablemonitor (name sysname, rows bigint, reserved varchar(100), data varchar(100), index_size varchar(100), unused varchar(100), datecollected datetime default getdate())

insert into tablemonitor (name, rows, reserved,data,index_size,unused) exec...

You will need to set the job to log to an output file then in the properties of the job which will capture the full output so that it can...

I have a 4 node cluster, with 3 SQL instance, the node names are CH4N1, CH4N2, CH4N3, CH4N4, the SQL instances are called CH4SQL1\INSTANCE01, CH4SQL2\INSTANCE02, CH4SQL3\INSTANCE03, my MsDtsSrvr.ini file looks...

No, you just need to put the TWONODECLUSTER in place of the . in the XML file on each server,

<?xml version="1.0" encoding="utf-8"?>

<DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown>

<TopLevelFolders>

...

The output of the text in the log file viewer for a job is only the top X amount of characters, the error will be somewhere else down the output,...

You have a virtual name specified when setting up a SQL instance on a cluster, this may be a named instance it maybe the default instance, but it is that...

. takes in the computer name not the virtual SQL computer name.

So in a 2 node setup take the following example (Node1, Node2, SQLName)

If SQLName is running on Node1 if...

Still doesnt matter as it installs the xml config file as .\instance where . is the actual local machine name not the virtual sql name, so it still wont connect...

cast the inner sum as decimal then case the whole output as varchar

You will need to convert it to a data type which allows you to specify the amount of decimal places you want, you would want decimal with the correct precision...

The code is sound when looked at in the editior but due to it being a XML character it strips it out in the main view.

If you remove the spaces...

I've see this when using a 32 bit driver on a 64 bit SQL server, but not with a 64 bit driver, so I'm at a stump now.