RE: Isolating a DTS package
From: Joseph Sack (JosephSack_at_discussions.microsoft.com)
Date: 12/21/04
- Next message: MS User: "Excel - named ranges"
- Previous message: Ilya Margolin: "Re: Steps did not run"
- In reply to: shop_at_pacifictabla.com: "Isolating a DTS package"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 21 Dec 2004 07:59:05 -0800
Hi Kayda,
There isn't a GUI method within SQL Server 2000 DTS to enable this
functionality, however you can build in custom Transact-SQL logic instead.
For example, you can create a DTS package status table that gets logged to
at the beginning and the end of your DTS package execution. Create 'Execute
SQL' tasks to validate whether or not the package should continue a specific
workflow based on the values in this table. If the last status was a
completed execution, the DTS package is safe to run. If the last status is
still open-ended, you may assume that there is already a DTS package
executing.
In SQL Server 2005, we will have a DTS Service that will allow us to monitor
all executing packages for a specific SQL Server instance.
Best Regards,
Joe Sack
Author of "SQL Server 2000 Fast Answers..."
http://www.JoeSack.com
"shop@pacifictabla.com" wrote:
> Hello:
>
> Simple question from a relative DTS newbie. When a DTS package is
> running, I want to make sure that the only thing that can update the
> tables is the package, and that the package cannot be run by anyone
> else while that instance of the package is running. What is the best
> setting for this?
>
> Thanks,
>
> Kayda
>
>
- Next message: MS User: "Excel - named ranges"
- Previous message: Ilya Margolin: "Re: Steps did not run"
- In reply to: shop_at_pacifictabla.com: "Isolating a DTS package"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
