| Author |
Write to db and transaction type
|
|
|
| Hi
I have an orchestration that first writes values to a database. Later in the
orchestration i update these values using another stored procedure. The
problem is that the update doesn't always work. I'm not sure way but one
theory is that the database row havn't been created yet when i try to update
it. Is this solved by using transaction types in scopes?
Thanks
| |
|
| Hmm, can anyone at least give me an indication that I am on the right way
here...?
"pez" wrote:
> Hi
>
> I have an orchestration that first writes values to a database. Later in the
> orchestration i update these values using another stored procedure. The
> problem is that the update doesn't always work. I'm not sure way but one
> theory is that the database row havn't been created yet when i try to update
> it. Is this solved by using transaction types in scopes?
>
> Thanks
| |
| Matt Milner 2005-09-09, 5:52 pm |
| Try using Delivery Notification on the first send. This should allow you to
know that your first message has been delivered before you get to sending
the second.
Matt
"pez" <pez@discussions.microsoft.com> wrote in message
news:BC7E4180-60AD-4ACE-B465-0AD3D9C75829@microsoft.com...[vbcol=seagreen]
> Hmm, can anyone at least give me an indication that I am on the right way
> here...?
>
> "pez" wrote:
>
| |
|
| How do I do that?
"Matt Milner" wrote:
> Try using Delivery Notification on the first send. This should allow you to
> know that your first message has been delivered before you get to sending
> the second.
>
> Matt
>
>
> "pez" <pez@discussions.microsoft.com> wrote in message
> news:BC7E4180-60AD-4ACE-B465-0AD3D9C75829@microsoft.com...
>
>
>
|
|
|
|