dbTalk Databases Forums  

DTS package stored in SQLServer vs. Structured Storage File

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


Discuss DTS package stored in SQLServer vs. Structured Storage File in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Andy
 
Posts: n/a

Default DTS package stored in SQLServer vs. Structured Storage File - 11-16-2004 , 10:32 AM






Hi All!

What are cons and pros between DTS packages stored in SQLServer vs.
Structured Storage File

Can a package stored as Structured Storage File be edited in
Enterprise Manager? How can it be opened?

Thank you in advance

Reply With Quote
  #2  
Old   
Darren Green
 
Posts: n/a

Default Re: DTS package stored in SQLServer vs. Structured Storage File - 11-16-2004 , 11:47 AM






How do I open a file package or template
(http://www.sqldts.com/default.aspx?289)

The package object is exactly the same, it is just what you prefer for
storage locations. Do you like using VSS for example to hold files or would
you prefer to manage it in a DB, and have the option of moving between DBs
rather than files.

The choice is yours.


--
Darren Green
http://www.sqldts.com
"Andy" <net__space (AT) hotmail (DOT) com> wrote

Quote:
Hi All!

What are cons and pros between DTS packages stored in SQLServer vs.
Structured Storage File

Can a package stored as Structured Storage File be edited in
Enterprise Manager? How can it be opened?

Thank you in advance



Reply With Quote
  #3  
Old   
Jack Peacock
 
Posts: n/a

Default Re: DTS package stored in SQLServer vs. Structured Storage File - 11-16-2004 , 07:38 PM



"Andy" <net__space (AT) hotmail (DOT) com> wrote

Quote:
Hi All!

What are cons and pros between DTS packages stored in SQLServer vs.
Structured Storage File

I use a file when an update has to go to source code control, or when I have
to move a package to another server. Once a package is ready for production
I save it in the server before setting up a schedule to run it. In short:
file for development, server for production.
Jack Peacock




Reply With Quote
  #4  
Old   
Andy
 
Posts: n/a

Default Re: DTS package stored in SQLServer vs. Structured Storage File - 11-17-2004 , 09:58 AM



"Jack Peacock" <peacock (AT) simconv (DOT) com> wrote

Quote:
"Andy" <net__space (AT) hotmail (DOT) com> wrote in message
news:edb90340.0411160832.760c132d (AT) posting (DOT) google.com...
Hi All!

What are cons and pros between DTS packages stored in SQLServer vs.
Structured Storage File

I use a file when an update has to go to source code control, or when I have
to move a package to another server. Once a package is ready for production
I save it in the server before setting up a schedule to run it. In short:
file for development, server for production.
Jack Peacock
Does it create overhead for SQL Server when a package stored in the server runs?


Reply With Quote
  #5  
Old   
Jack Peacock
 
Posts: n/a

Default Re: DTS package stored in SQLServer vs. Structured Storage File - 11-17-2004 , 02:57 PM



"Andy" <net__space (AT) hotmail (DOT) com> wrote

Quote:
Does it create overhead for SQL Server when a package stored in the server
runs?

Not that I've noticed, but my jobs tend to be disk or network bound
(limitations on remote server thruput) so the CPU usage is fairly low
anyway. There can be problems with having the right user profile when the
job runs. If I use a DTS package that depends on mapped drives I run it as
a file, Scheduled Task with DTSRUN, to make sure the user and shares are set
up right.
Jack Peacock




Reply With Quote
  #6  
Old   
Darren Green
 
Posts: n/a

Default Re: DTS package stored in SQLServer vs. Structured Storage File - 11-17-2004 , 04:01 PM



In message <edb90340.0411170758.6b8d7fe1 (AT) posting (DOT) google.com>, Andy
<net__space (AT) hotmail (DOT) com> writes
Quote:
"Jack Peacock" <peacock (AT) simconv (DOT) com> wrote in message
news:<#WGOaYEzEHA.1260 (AT) TK2MSFTNGP12 (DOT) phx.gbl>...
"Andy" <net__space (AT) hotmail (DOT) com> wrote in message
news:edb90340.0411160832.760c132d (AT) posting (DOT) google.com...
Hi All!

What are cons and pros between DTS packages stored in SQLServer vs.
Structured Storage File

I use a file when an update has to go to source code control, or when I have
to move a package to another server. Once a package is ready for production
I save it in the server before setting up a schedule to run it. In short:
file for development, server for production.
Jack Peacock

Does it create overhead for SQL Server when a package stored in the
server runs?
The overhead is a single call, which basically is a SELECT MyPackageData
FROM sysdtspackages where package = mypkg, so no.

The overhead comes on the machine which executes the package and any
machines used as sources and destinations, which will be exactly the
same regardless of the storage location.

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org



Reply With Quote
Reply




Thread Tools
Display Modes

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.