Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««1234»»»

SSIS in cluster setup Expand / Collapse
Author
Message
Posted Friday, November 2, 2012 7:41 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 9:02 AM
Points: 387, Visits: 954
Anthony, really appreciate your answers. you made it to easy to understand.

Why the grumpy look?

Mr/Ms "want a cool Sig"

Thanks to you too. Your post gave me a starting point and made me to probe. Thanks for the link.

Thanks mates
Post #1380369
Posted Friday, November 2, 2012 8:25 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 9:02 AM
Points: 387, Visits: 954
A strange doubt popped up now. Installing SSIS on each node is needed for importing packages to msdb (in addition to managing packages in msdb while failover).?

If i dont have an need to manage packages from management studio, then i dont have to install SSIS on each node. Is this correct?
Post #1380659
Posted Monday, November 5, 2012 1:49 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 6:52 AM
Points: 5,131, Visits: 4,918
No, you can use the command line based tool instead to upload the package if you dont want to do it via SSMS, that way you wont need the SSIS service.

Check what the service does and then decide do I really need to do any of them things, if yes you need the service, if no then you dont.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1380911
Posted Monday, November 5, 2012 2:30 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 9:02 AM
Points: 387, Visits: 954
Anthony,

SSIS packages wouldbe run from agent jobs. Now i dont need to run or monitor ssis packges from management studio. I wont be installating SSIS on each nodes.

in case of failover, packages running would fail/cancel. After failing over to 2nd node, future scheduled packages would run. is this correct? If this is correct, then for running ssis packages only, we need to run as agent jobs, no need to install ssis or change xml or make ssis cluster resource. Am i right?
Post #1380932
Posted Monday, November 5, 2012 2:33 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 6:52 AM
Points: 5,131, Visits: 4,918
Yes on fail over if they are running as jobs then yes they will run as intended.

If you fail over and want to upload a new SSIS package you will need to do it via the command line tool, not via SSMS.

You just need to decide on if you will use the functionality of the SSIS service and if you do then install it or not.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1380933
Posted Monday, November 5, 2012 2:38 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 9:02 AM
Points: 387, Visits: 954
Anthony,

You are amazing. Thanks much for the answers.
Post #1380935
Posted Monday, November 5, 2012 5:56 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 9:02 AM
Points: 387, Visits: 954
guys,

Doubts keep creeping up at each step:-(

My cluster is default, not named. since, i connect to it using system name and not as systemname\instancename. so my assumption is that it is a default installed cluster.

"ssis connects to default intance in which the ssis service is running"... what this mean in terms of 2 node cluster?
Post #1381035
Posted Monday, November 5, 2012 6:01 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 6:52 AM
Points: 5,131, Visits: 4,918
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 and you would have to modify the xml file.



Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1381036
Posted Monday, November 5, 2012 6:19 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 9:02 AM
Points: 387, Visits: 954
My xml file has the default setup like
<Name>MSDB</Name>
<ServerName>.</ServerName>
....

this means that now it connects to default (active) server and on failover the passive becomes active and it should be the default instance now. why it is not like that?
Post #1381041
Posted Monday, November 5, 2012 6:23 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 6:52 AM
Points: 5,131, Visits: 4,918
. 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 you try to connect to . it tries to connect to a SQL server called Node1 not SQLName, same if it fails over it now looks for . as Node2 not SQLName.

Now in a standalone setup where the SQLName is the same as the Node name your ok, but in a cluster its not the same.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1381043
« Prev Topic | Next Topic »

Add to briefcase ««1234»»»

Permissions Expand / Collapse