I am creating a DTS package to archive records from one table to another, given a certain lower and upper row count.

These lower and upper values need to be dynamic, and if possible used as global variables.

In essence, in VBScript I would like to have the individual executing the package to be asked if the current lower and upper global variables are acceptable, if not then be able to modify their values.

I currently have some global variables created in Execute SQL Task steps. I can see and use them, but how do I create global variables that are independent of a SQL Task?

--
Message posted via http://www.sqlmonster.com

Global Variables are not aligned to a Task they are at the package level.

In your package you can then use them in a task if you so wish.

It is generally considered bad practice to ask a user for something in the
middle of a package. This invites the "Lunchtime Lock". I personally would
grab the variable values up front in a client app. Ask the user. Change if
necesary. I do not know how you calll the package but there are numerois
ways to pass the new values.

--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


"Robert Richards via SQLMonster.com" <forum (AT) SQLMonster (DOT) com> wrote