Mark Forums Read

DTS Package Migration in SQL 2000

Go Back

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts

Reply

#1

Old

Giri Palakodeti

Posts: n/a

DTS Package Migration in SQL 2000 - 10-22-2008 , 09:26 AM

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

Reply With Quote

#2

Old

Russell Fields

Posts: n/a

Re: DTS Package Migration in SQL 2000 - 10-23-2008 , 02:22 PM

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 (AT) discussions (DOT) microsoft.com> wrote in
message news:F94DB5D2-4B89-43C9-98F7-66D641AB9261 (AT) microsoft (DOT) com...

Quote:

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

Reply With Quote

#3

Old

Russell Fields

Posts: n/a

Re: DTS Package Migration in SQL 2000 - 10-23-2008 , 02:22 PM

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 (AT) discussions (DOT) microsoft.com> wrote in
message news:F94DB5D2-4B89-43C9-98F7-66D641AB9261 (AT) microsoft (DOT) com...

Quote:

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

Reply With Quote

#4

Old

Russell Fields

Posts: n/a

Re: DTS Package Migration in SQL 2000 - 10-23-2008 , 02:22 PM

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 (AT) discussions (DOT) microsoft.com> wrote in
message news:F94DB5D2-4B89-43C9-98F7-66D641AB9261 (AT) microsoft (DOT) com...

Quote:

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

Reply With Quote

#5

Old

Russell Fields

Posts: n/a

Re: DTS Package Migration in SQL 2000 - 10-23-2008 , 02:22 PM

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 (AT) discussions (DOT) microsoft.com> wrote in
message news:F94DB5D2-4B89-43C9-98F7-66D641AB9261 (AT) microsoft (DOT) com...

Quote:

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

Reply With Quote

#6

Old

Russell Fields

Posts: n/a

Re: DTS Package Migration in SQL 2000 - 10-23-2008 , 02:22 PM

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 (AT) discussions (DOT) microsoft.com> wrote in
message news:F94DB5D2-4B89-43C9-98F7-66D641AB9261 (AT) microsoft (DOT) com...

Quote:

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

Reply With Quote

#7

Old

Russell Fields

Posts: n/a

Re: DTS Package Migration in SQL 2000 - 10-23-2008 , 02:22 PM

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 (AT) discussions (DOT) microsoft.com> wrote in
message news:F94DB5D2-4B89-43C9-98F7-66D641AB9261 (AT) microsoft (DOT) com...

Quote:

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

Reply With Quote

#8

Old

Russell Fields

Posts: n/a

Re: DTS Package Migration in SQL 2000 - 10-23-2008 , 02:22 PM

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 (AT) discussions (DOT) microsoft.com> wrote in
message news:F94DB5D2-4B89-43C9-98F7-66D641AB9261 (AT) microsoft (DOT) com...

Quote:

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

Reply With Quote

#9

Old

Russell Fields

Posts: n/a

Re: DTS Package Migration in SQL 2000 - 10-23-2008 , 02:22 PM

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 (AT) discussions (DOT) microsoft.com> wrote in
message news:F94DB5D2-4B89-43C9-98F7-66D641AB9261 (AT) microsoft (DOT) com...

Quote:

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

Reply With Quote

Reply

« Previous Thread | Next Thread »

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Posting Rules
You may not post new threads You may not post replies You may not post attachments You may not edit your posts vB code is On Smilies are On [IMG] code is On HTML code is Off

Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.