all groups > sql server dts > june 2005 >
You're in the

sql server dts

group:

Scheduled Package dose not being instanciated more than once


Scheduled Package dose not being instanciated more than once J-T
6/17/2005 3:06:14 PM
sql server dts:
I have a Parent package which call different child packages.I have schaduled
the Parent package to be executed evey 3 minutes and I'm using a Table in
which I insert the name of the child package which is working and when it is
done I delete the row,by this mechanism I control not 2 child packages get
executed at the same time(Because they do transactional things on their own
table, and I won;t tend to be stuck in deadlocks).

Problem is that I am expecting that two different child packages could be
executed at the same time but for some reason when Parent package call one
child package and it takes more than 3 minutes,none of the other packages
run.There is no any other instance of Parent package running.

When I schadule something ,it is supposed to be run at an specific interval
right?

Thanks

Re: Scheduled Package dose not being instanciated more than once Allan Mitchell
6/18/2005 11:53:10 AM
The same job cannot be run more than once at the same time.

A way to control child package exeution would be to link them through
workflow wouldn't it?


--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


[quoted text, click to view]

Re: Scheduled Package dose not being instanciated more than once J-T
6/18/2005 7:04:14 PM
Hi Allan,

My parent package is a separte package than the child packages.I load the
package based on the CSV file which is recieved in Parent package,then in an
Activex script I load the appropriate package.

[quoted text, click to view]
What a pitty,I thought it could be.Now the only option I have is that I can
create two or three jobs of my Parent Package,can I? My only concern is that
child packages logging the validation errors in one Table (That table is
shared between all the child packages).Will I be stuck in dead lucks or
something? I insert the log records by calling a stored procedure (no
transaction involved) in child packages(there is a Execute SQL Task in each
child package which referes to that stored procedure).

Thanks for your help Allan (as always:-))

Cheers,


[quoted text, click to view]

Re: Scheduled Package dose not being instanciated more than once Allan Mitchell
6/19/2005 8:38:33 AM
The same package cn be called at the same time multiple times.

OK so what I think you are trying to do is this

Fire a DTS package every 3 minutes (Parent)
In the parent package you check a csv file. Based on the CSV file you call
a package(Child)

I am not sure how you do the check here.

Would it be possible for you to fire the package based on an event? The
file being dropped?


--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


[quoted text, click to view]

Re: Scheduled Package dose not being instanciated more than once J-T
6/21/2005 11:55:52 AM
Thanks Allan,

My idea is now working.I schaduled the Parent package twice to be executed
after 3 minutes (I have two jobs of the same parent package).As I siad child
packages write their logs into a common table using a stored proc (with one
simple insert and no transaction).Apparently everything is fine.

[quoted text, click to view]
I have information about each file in database ,and based on that
information I decide which package I should execute.In the meantime I use a
table to keep track of executing packages and by using that table I won;t
let two instance of the same package run at the same time.Reason is that In
child packages I call stored procedures which use Transactions and I don;t
wnt to be tarpped by deallock or stuff like this ,that's why I came up with
the idea of not letting two instances of the same child package run at the
same time ,but I can have differnet instances of the child packages working
simultaniously .

Makes sense?

Thanks
[quoted text, click to view]

AddThis Social Bookmark Button