I have some DTS packages, which import text files into a database. The
text file names change every month, so the packages gets re-saved every
month - there are about 60 saves per month.

The question is - will this fill up my sysdtspackages table? Do I need
to consider truncating it occasionally?

TIA

Lewis Veale
lewisdotvealeatpdms.com
www.pdms.com

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Yep you have noted a subtlety of DTS. Even though you save as the same name
and to all intents and purposes top the casual viewer it is the same
package, for the same of sysdtspackages it is another entry.

Parameterise the name of the text file and assign it to the package from
outside i.e. when you call it.

This way you will never need to change the package just because the name of
the file changes.

You can use

Dynamic Properties Task
/A switch to DTSRUN
Object Model



--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.allisonmitchell.com - Expert SQL Server Consultancy.
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"Lewis" <lewisdotvealeatpdms.com> wrote

Thanks for the reply.

I'm on SQL Server 7. Can I use parameters?

Lewis Veale
lewisdotvealeatpdms.com
www.pdms.com

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Ughh No.

This is a good reason to post the version of your SQL Server installation.

You are still able to have fun with this though

1. Call the package using the Object model and change the settings in there
2. Store the settings in a DB table and use a Datapump to assign that to a
GV and then the connection
3. Use ADO in an Active Script task to assign the value to a GV



--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.allisonmitchell.com - Expert SQL Server Consultancy.
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"Lewis" <lewisdotvealeatpdms.com> wrote

In message <ehYfMFk8DHA.452 (AT) TK2MSFTNGP11 (DOT) phx.gbl>, Lewis
<lewisdotvealeatpdms.com@?.?.invalid> writes
so much, but I would still consider clearing old versions after a period
of time. This can be done through the UI, open the versions dialog by
right-clicking a package and click delete. You can also just delete rows
from sysdtspackages, but be careful. I don't do it on a regular basis,
but when I have I normally use the createdate field to remove all prior
to a certain date or only keep n versions *per* package. Packages can
take up quite a lot of space over time.

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

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

Thanks - both of you. I think I will modify my package so I don't have
to re-save it each time - this will also eliminate another problem I
have with package ownership (which Darren has already helped me out with
- thanks again!).

Its worth mentioning, I think, that Darrens extremely useful DTSBackup
tool - available from www.sqldts.com - only transfers the latest version
of a package - which is ideal when transferring packages from
development to beta and live.

Cheers

Lewis Veale
lewisdotvealeatpdms.com
www.pdms.com

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!