Re: DTS Package Migration in SQL 2000
- From: "Russell Fields" <russellfields@xxxxxxxxxx>
- Date: Thu, 23 Oct 2008 15:22:40 -0400
Giri,
If you save your DTS package as a Structured Storage File, it will create a
file that can be given to your DBA. He can then either edit it and resave
it in the production SQL Server, or just run if from the file.
Of course, it is also likely that some references, such as the connections,
may need to be updated.
FWIW, although storing in SQL Server has some advantages, because of the
issues of deployment as well as more than one person having rights to update
the DTS package, I almost always use Structured Storage Files. (Of course,
that means managing the security properly for the folder where your DTS
package is stored.)
RLF
"Giri Palakodeti" <GiriPalakodeti@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:F94DB5D2-4B89-43C9-98F7-66D641AB9261@xxxxxxxxxxxxxxxx
I have created a DTS package on my TEST server in SQL 2K. I want to move
this
package to PROD. I cannot script and hand over it to my DBA.
What is the best practice and I have only package to move to prod.
Thanks in anticipation
.
- References:
- DTS Package Migration in SQL 2000
- From: Giri Palakodeti
- DTS Package Migration in SQL 2000
- Prev by Date: To run a excel macro using DTS package in sql server 2000
- Next by Date: Dynamically Create SQL Fields in SSIS 2005
- Previous by thread: DTS Package Migration in SQL 2000
- Next by thread: To run a excel macro using DTS package in sql server 2000
- Index(es):
Relevant Pages
|
