Doubt in Transaction Scope

Hi ,

I have 2 packages and they get executed in SQL Job.

Each of these package will have seperate transactions with the Database and I am not sure of how to maintain the transactions between these 2 packages.

Can someone explain me the necessary setting to achieve this. If I set the TransactionOption property to Required (or) Supported in both these packages, will the Transaction Scope of the first package extend to the second one.

For me, If the second package ends up in error, the first package should also have to be rollbacked.

Any suggestions would be of great help.

Thanks

Evan

Are the two packages setup so that one is parent and the other is child?

Otherwise, I'm not sure how you can enforce transactions. If so, then set each to "Required" and be sure to set the FailParentOnFailure property to true in the child so that when it fails, so does the parent.

Does the Sql Server 2005 EVAL distribution support run of packages under DtExec?

I believe I have made a complete install of Sql Server 2005 on my dev. machine, including all client tools, and can run SSIS packages from the dev. environment.

However DtExec refuses to run any package and always throws the "insufficient version" error (as does the "RunPackage" component, probably for the same reason).

I have repeatedly attempted to find something more to install from the Sql Server 2005 eval release that will allow DTExec to run without the "insufficient version" error, but can find nothing else to install from the eval. The install wizard (and the "change" wizard) indicates everything is installed and will not build a list of any additional components to install.

Are we sure that DtExec will install and run from a sql server 2005 eval distribution?

Licenses are in the pipeline (not that pipleine) but we need to start testing our SSIS solution in the meantime.

p.s. Kudos to the dev. team, it really is an excellent tool!

Thanks,

Ken

This sounds like the SSIS services feature is missing, you may just have the workstation components. If running on a workstation OS, then this can be an issue-

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=112469&SiteID=1

|||

Thanks for the reply Darren.

The O.S. is Windows 2000 Advanced Server, and to the best of my ability I have confirmed and reconfirmed that every possible installable component and piece of software provided in the Sql Server 2005 eval. distro. has been fully installed in the runtime environment in question.

I recently used the same Sql Server 2005 distro. to perform an identical install onto an XP Pro machine and DtExec seems to run fine.

So I will assume I have some kind of flawed installation on the win2k advanced server box and will try a complete deinstall and reinstall as my last resort.