+972 52-548-6969
I have two SSIS packages that cannot run concurrently, however, one must run once every 5 minutes, and the second every hour, so they are assured to conflict very soon. I can handle this situation manually, but I wanted to know if there was a builtin way to handle that.
Markdown turns plain text formatting into fancy HTML formatting.
*italic* **bold**
_italic_ __bold__
Inline:
An [example](http://url.com/ "Title")
Reference-style labels (titles are optional):
An [example][id]. Then, anywhere
else in the doc, define the link:
[id]: http://example.com/ "Title"
Inline (titles are optional):
Reference-style:
![alt text][id]
[id]: /url/to/img.jpg "Title"
Setext-style:
Header 1
========
Header 2
--------
atx-style (closing #'s are optional):
# Header 1 #
## Header 2 ##
###### Header 6
Ordered, without paragraphs:
1. Foo
2. Bar
Unordered, with paragraphs:
* A list item.
With multiple paragraphs.
* Bar
You can nest them:
* Abacus
* answer
* Bubbles
1. bunk
2. bupkis
* BELITTLER
3. burper
* Cunning
> Email-style angle brackets
> are used for blockquotes.
> > And, they can be nested.
> #### Headers in blockquotes
>
> * You can quote a list.
> * Etc.
Three or more dashes or asterisks:
---
* * *
- - - -
End a line with two or more spaces:
Roses are red,
Violets are blue.
Code blocks delimited by 3 or more backticks or tildas:
```
This is a preformatted
code block
```
Set the id of headings with {#<id>} at end of heading line:
## My Heading {#myheading}
Fruit |Color
---------|----------
Apples |Red
Pears |Green
Bananas |YellowTerm 1
: Definition 1
Term 2
: Definition 2Body text with a footnote [^1]
[^1]: Footnote text here
MDD <- will have title
*[MDD]: MarkdownDeep
There are posts all the way to May 21, 2018
| Main feed | |
| Comments feed |
Comments
Hmmm ... starting simply (and assuming your contending resource is a DB table):
BEGIN TRANSACTION
Matt,
I need to avoid doing a database - wide lock, which is what would happen when those monsters are running.
I also need to touch more than a single DB / resource, and a distributed transaction is not an option here.
Your situation warrants re-inventing distributed transactions, but not using them ?
/Mats
Mats,
Absolutely not!
I just need to ensure a serial execution of packages, nothing more. Transaction semantics are need to be more fine grained than a transaction per the entire package.
I wanted to know if there was a builtin way to provide the: "when package A runs, wait to run B, and vice versa"
Perhaps a better term is:
Do not run packages A,B,C in parallel
You can create a third package that runs those two packages in serial. For the one, you only want to run once a hour, you use some variable or if-statement,
Comment preview