SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSIS in cluster


SSIS in cluster

Author
Message
george sibbald
george sibbald
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10292 Visits: 13687
@DHeath

my feeling at the moment is we have a misunderstanding of clustering rather than a cluster issue, seems a bit early to start advocating rebuilding it. :-)

@peacesells

SQLAgent jobs are held in msdb and there is only one msdb per instance. You seem fixated on the nodes, is this a failover cluster with just one instance, or do you have two instances, one active on each node? (An active\active cluster)

---------------------------------------------------------------------
peacesells
peacesells
Old Hand
Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)

Group: General Forum Members
Points: 338 Visits: 1481
george sibbald (7/15/2013)
@DHeath


@peacesells

SQLAgent jobs are held in msdb and there is only one msdb per instance. You seem fixated on the nodes, is this a failover cluster with just one instance, or do you have two instances, one active on each node? (An active\active cluster)



This is a fail over cluster with two nodes - with each node having two instances of sql server. Its Active/Passive.
george sibbald
george sibbald
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10292 Visits: 13687
each node with two instances gives you 4 instances, and that is very much active\active, or as I believe Microsoft would officially call it, a multi-instance cluster.

You will have to put the jobs into the msdb relevant to the database the job is for, so just log onto the correct database engine and create the job via SQLAgent for that instance, using the virtual SQL name.

The link I posted shows you how to manage multi instances, its just a case of adding new xml nodes for each msdb and\or file system if you are using the file system to store the packages. NAme them so you can readily identify which is which when you open SSIs via management studio.

---------------------------------------------------------------------
DHeath
DHeath
Old Hand
Old Hand (395 reputation)Old Hand (395 reputation)Old Hand (395 reputation)Old Hand (395 reputation)Old Hand (395 reputation)Old Hand (395 reputation)Old Hand (395 reputation)Old Hand (395 reputation)

Group: General Forum Members
Points: 395 Visits: 650
Much much clearer now that its known this is a active/active cluster. Had me wondering there for a few minutes but wanted to make sure it was verified and i am sure George is your man with the answers here :-)

DHeath
peacesells
peacesells
Old Hand
Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)

Group: General Forum Members
Points: 338 Visits: 1481
george sibbald (7/16/2013)
each node with two instances gives you 4 instances, and that is very much active\active, or as I believe Microsoft would officially call it, a multi-instance cluster.

You will have to put the jobs into the msdb relevant to the database the job is for, so just log onto the correct database engine and create the job via SQLAgent for that instance, using the virtual SQL name.

The link I posted shows you how to manage multi instances, its just a case of adding new xml nodes for each msdb and\or file system if you are using the file system to store the packages. NAme them so you can readily identify which is which when you open SSIs via management studio.



George,

Clearly i am not a cluster aware guy- but nonetheless very interesting subject if you can figure your way through.

I read somewhere that sql server agent was cluster aware which interprets to me that it if i need a job running in one of the instances on both nodes- will it suffice to create a job in one of the instances of the job using the virtual name and should that node fail the job is also visible on the same instance on the other node.

For instance I have nodeA with (instanceD,InstanceF) ANd NodeB with (instanceD,InstanceF). Now i only need a sql server agent job running on InstanceD on both nodes. My understanding is that i don't have to create the job on both nodes for those two instances-please correct me.

Since i am doing a file system deployment (my package would reside in shared disk), i do not see my packages in MSDB-should i be worried?

Thank You for your time-appreciate it.
george sibbald
george sibbald
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10292 Visits: 13687
peacesells (7/16/2013)
george sibbald (7/16/2013)
each node with two instances gives you 4 instances, and that is very much active\active, or as I believe Microsoft would officially call it, a multi-instance cluster.

You will have to put the jobs into the msdb relevant to the database the job is for, so just log onto the correct database engine and create the job via SQLAgent for that instance, using the virtual SQL name.

The link I posted shows you how to manage multi instances, its just a case of adding new xml nodes for each msdb and\or file system if you are using the file system to store the packages. NAme them so you can readily identify which is which when you open SSIs via management studio.



George,

Clearly i am not a cluster aware guy- but nonetheless very interesting subject if you can figure your way through.


don't worry, you're not the only one



I read somewhere that sql server agent was cluster aware which interprets to me that it if i need a job running in one of the instances on both nodes- will it suffice to create a job in one of the instances of the job using the virtual name and should that node fail the job is also visible on the same instance on the other node.


correct



For instance I have nodeA with (instanceD,InstanceF) ANd NodeB with (instanceD,InstanceF). Now i only need a sql server agent job running on InstanceD on both nodes. My understanding is that i don't have to create the job on both nodes for those two instances-please correct me.



correct, you only need to create the job once on the virtual instance


Since i am doing a file system deployment (my package would reside in shared disk), i do not see my packages in MSDB-should i be worried?


nope, that would be expected, you would have to physically import the package into msdb (via SSIS) to se it in msdb.

msdb is usually the better place to store packages, but its not a golden rule, you may want to investigate why the file system has been chosen.

You have a 2 instance cluster which is currently active\passive only because both instances are live on the same node. It is perfectly possible for just one instance to failover in which case you would then be active\active. So reaally its clearer to call it muti-instance.

[/quote]

---------------------------------------------------------------------
peacesells
peacesells
Old Hand
Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)Old Hand (338 reputation)

Group: General Forum Members
Points: 338 Visits: 1481
[/quote]

nope, that would be expected, you would have to physically import the package into msdb (via SSIS) to se it in msdb.

msdb is usually the better place to store packages, but its not a golden rule, you may want to investigate why the file system has been chosen.

You have a 2 instance cluster which is currently active\passive only because both instances are live on the same node. It is perfectly possible for just one instance to failover in which case you would then be active\active. So reaally its clearer to call it muti-instance.

[/quote][/quote]


<?xml version="1.0" encoding="UTF-8"?>
<DtsServiceConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown> <TopLevelFolders>
<Folder xsi:type="SqlServerFolder">
<Name>MSDB</Name>
<ServerName>sqlA\instanceA</ServerName>

</Folder> -<Folder xsi:type="SqlServerFolder">
<Name>MSDB</Name>
<ServerName>sqlB\InstanceB</ServerName>

</Folder> -<Folder xsi:type="FileSystemFolder">
<Name>File System</Name>
<StorePath>..\Packages</StorePath>
</Folder>
</TopLevelFolders>
</DtsServiceConfiguration>

I have two named instances (sqlA\instanceA & sqlB\InstanceB) in both nodes (MachineA and MachineB) and I make the following changes in MsDtsSrvr.ini.xml file in both machines.
My deployment method is file system -storing packages on a shared disk (SAN).I made changes as shown above and restarted SSIS services on both the nodes.
However, when I login to SSIS services from Management studion using the hostname (MachineA AND MachineB ), i see packages under filesystem only in MachineA, the same folder is empty on MachineB. Shouldn't the packages be visible there as well? I see two empty MSDB folder on both machines and if try to expand it - I get the extact error as show in the below link even after making changes in the ini file- what i am missing- thanks.
onclick:if_IFCode(''http://shahfaisalmuhammed.wordpress.com/tag/msdtssrvr-ini-xml/'');
george sibbald
george sibbald
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10292 Visits: 13687
that link does not expand for me.

MachineB (presumed passive node) will not be able to see the disks when passive so will not able to see the file system. Connect with virtual server name.

---------------------------------------------------------------------
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search