dbTalk Databases Forums  

Execute SSIS Pkg From MSMQ Trigger??

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Execute SSIS Pkg From MSMQ Trigger?? in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
gfergo@gmail.com
 
Posts: n/a

Default Execute SSIS Pkg From MSMQ Trigger?? - 12-13-2006 , 05:30 AM






Good Morning,

Has anyone successfully executed an SSIS package from within an MSMQ
trigger?

Environment -

We are running Windows 2003, .NET Framework 2.0, and Sql Server 2005.

Our trigger is written in C#. It has been registered using RegAsm. It
is running inside Component Services (Server activation).

Our SSIS package is in Sql Server. In the C# code we are using the
LoadFromSqlServer method described here -

http://msdn2.microsoft.com/en-us/lib...sqlserver.aspx

My questions -

1.) Is it better to load the SSIS into Sql Server and use
LoadFromSqlServer, or is it better to leave the *.dtsx file in a
directory and use LoadPackage? What are the advantages and
disadvantages of each?

2.) Assuming we keep our current architecture (C# trigger in MSMQ /
SSIS package inside Sql Server), must the MSMQ Trigger service run
under a specific account in order to load and execute the SSIS package?
What permissions would that account need?

3.) Can someone provide a code sample for executing the SSIS package?
More specifically, can someone demonstrate proper usage of the
DTSEvents?

Thank you!!!

Glen


Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Execute SSIS Pkg From MSMQ Trigger?? - 12-13-2006 , 04:06 PM






Hello gfergo (AT) gmail (DOT) com,


Here are some thoughts

1. For me it makes no difference. There are pluses and minuses on both
sides. Good discussion here

http://www.sqljunkies.com/WebLog/kni.../05/13523.aspx

2. The account will need to have permissions to retrieve the package from
its store wherever that may be and if using Windows Authentication in the
package connection manager will need to be able to satisy those needs as
well.

3. Have a look at this

http://forums.microsoft.com/MSDN/Sho...21443&SiteId=1


Regards

Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com

Quote:
Good Morning,

Has anyone successfully executed an SSIS package from within an MSMQ
trigger?

Environment -

We are running Windows 2003, .NET Framework 2.0, and Sql Server 2005.

Our trigger is written in C#. It has been registered using RegAsm.
It is running inside Component Services (Server activation).

Our SSIS package is in Sql Server. In the C# code we are using the
LoadFromSqlServer method described here -

http://msdn2.microsoft.com/en-us/lib...rver.dts.runti
me.application.loadfromsqlserver.aspx

My questions -

1.) Is it better to load the SSIS into Sql Server and use
LoadFromSqlServer, or is it better to leave the *.dtsx file in a
directory and use LoadPackage? What are the advantages and
disadvantages of each?

2.) Assuming we keep our current architecture (C# trigger in MSMQ /
SSIS package inside Sql Server), must the MSMQ Trigger service run
under a specific account in order to load and execute the SSIS
package?
What permissions would that account need?
3.) Can someone provide a code sample for executing the SSIS package?
More specifically, can someone demonstrate proper usage of the
DTSEvents?

Thank you!!!

Glen




Reply With Quote
  #3  
Old   
gfergo@gmail.com
 
Posts: n/a

Default Re: Execute SSIS Pkg From MSMQ Trigger?? - 12-14-2006 , 07:49 AM



Thank you Allan!!

Anyone else have any thoughts on this??

We'd love to see some sample code -- especially something that helps
explain how to properly implement and use the DTS Events interface.

Thanks!!

Glen




Allan Mitchell wrote:
Quote:
Hello gfergo (AT) gmail (DOT) com,


Here are some thoughts

1. For me it makes no difference. There are pluses and minuses on both
sides. Good discussion here

http://www.sqljunkies.com/WebLog/kni.../05/13523.aspx

2. The account will need to have permissions to retrieve the package from
its store wherever that may be and if using Windows Authentication in the
package connection manager will need to be able to satisy those needs as
well.

3. Have a look at this

http://forums.microsoft.com/MSDN/Sho...21443&SiteId=1


Regards

Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com

Good Morning,

Has anyone successfully executed an SSIS package from within an MSMQ
trigger?

Environment -

We are running Windows 2003, .NET Framework 2.0, and Sql Server 2005.

Our trigger is written in C#. It has been registered using RegAsm.
It is running inside Component Services (Server activation).

Our SSIS package is in Sql Server. In the C# code we are using the
LoadFromSqlServer method described here -

http://msdn2.microsoft.com/en-us/lib...rver.dts.runti
me.application.loadfromsqlserver.aspx

My questions -

1.) Is it better to load the SSIS into Sql Server and use
LoadFromSqlServer, or is it better to leave the *.dtsx file in a
directory and use LoadPackage? What are the advantages and
disadvantages of each?

2.) Assuming we keep our current architecture (C# trigger in MSMQ /
SSIS package inside Sql Server), must the MSMQ Trigger service run
under a specific account in order to load and execute the SSIS
package?
What permissions would that account need?
3.) Can someone provide a code sample for executing the SSIS package?
More specifically, can someone demonstrate proper usage of the
DTSEvents?

Thank you!!!

Glen



Reply With Quote
  #4  
Old   
gfergo@gmail.com
 
Posts: n/a

Default Re: Execute SSIS Pkg From MSMQ Trigger?? - 12-19-2006 , 08:25 AM



Anyone else have any thoughts on this?

We could really use some (working) code samples.

Thank you!

Glen




gfergo (AT) gmail (DOT) com wrote:
Quote:
Thank you Allan!!

Anyone else have any thoughts on this??

We'd love to see some sample code -- especially something that helps
explain how to properly implement and use the DTS Events interface.

Thanks!!

Glen




Allan Mitchell wrote:
Hello gfergo (AT) gmail (DOT) com,


Here are some thoughts

1. For me it makes no difference. There are pluses and minuses on both
sides. Good discussion here

http://www.sqljunkies.com/WebLog/kni.../05/13523.aspx

2. The account will need to have permissions to retrieve the package from
its store wherever that may be and if using Windows Authentication in the
package connection manager will need to be able to satisy those needs as
well.

3. Have a look at this

http://forums.microsoft.com/MSDN/Sho...21443&SiteId=1


Regards

Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com

Good Morning,

Has anyone successfully executed an SSIS package from within an MSMQ
trigger?

Environment -

We are running Windows 2003, .NET Framework 2.0, and Sql Server 2005.

Our trigger is written in C#. It has been registered using RegAsm.
It is running inside Component Services (Server activation).

Our SSIS package is in Sql Server. In the C# code we are using the
LoadFromSqlServer method described here -

http://msdn2.microsoft.com/en-us/lib...rver.dts.runti
me.application.loadfromsqlserver.aspx

My questions -

1.) Is it better to load the SSIS into Sql Server and use
LoadFromSqlServer, or is it better to leave the *.dtsx file in a
directory and use LoadPackage? What are the advantages and
disadvantages of each?

2.) Assuming we keep our current architecture (C# trigger in MSMQ /
SSIS package inside Sql Server), must the MSMQ Trigger service run
under a specific account in order to load and execute the SSIS
package?
What permissions would that account need?
3.) Can someone provide a code sample for executing the SSIS package?
More specifically, can someone demonstrate proper usage of the
DTSEvents?

Thank you!!!

Glen



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.