Hi
I have a DTS package which is being moved from development to Production
environment. I would like to set the IP address of the target sql server
database with a parameter which can be set when it is moved to production.
How can I achieve this.

Thanks
Bob

Hello Bob,

Ideally you will have set up in your package a Dynamic Properties task that
reads from an external source, or you will have used a variable in the package
to populate this property. This way you can use the /A switch to DTSRun


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Bob,

Although I like Allan's reply, I would like to stress that you can use the
same database server name in development and in production.

There are a number of ways to do so:
- If the DNS server in production is different than in development, just
create an entry in each one with the same name and pointing on the two
different IP addresses.
- Alternatively, you can edit the host file (%SYSTEM%\drivers\etc) of the
development and production servers that host your package, create a unique
alias for the two DB servers
- Create an alias in the "SQL Native Client Configuration" on both the
development and production servers that host your package

BTW, I would not use the IP address of a server. It is always advisable to
create a DNS entry for the server. That way, if you have to switch servers
because of a catastrophic failure, the re-configuration is painless.

That way, the package stays the same, no matter which environment it runs
in.

Good luck,

Philippe Lacoude


"Bob" <Bob (AT) discussions (DOT) microsoft.com> wrote

Just wanted to bounce this possible third option off you guys as well...I'm
new to DTS, but would a data link connection also work in this situation?
You could keep your connections in a separate data link file (*.udl) that you
could just edit as the server changes.

"Bob" wrote:

Thank you for the reply. Can you please be more specific. I would like to
know how to give paramaters for username, password, datasource and servername
to my DTS packages so that once they are moved to production. They can be set
and run immediately.

Thanks


"Philippe Lacoude" wrote: