"Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
news:umJM7kEGFHA.1932@TK2MSFTNGP14.phx.gbl...
> Nice trick
>
> You can also create an alias using cliconfg and use the same way.
>
> As for the original post of can you move and change in one go then the
> answer is no.
>
> Ideally things like Servername should be as has been mentioned i.e.
> controlled outside of the package or you should set the package up to
> look somewhere to fond the server names and then set internally.
>
>
>
>
> "eenstrom@optonline.net" <eenstrom@optonline.net> wrote in message
> news:eenstrom@optonline.net:
> > eleftheriak@hotmail.com wrote:
> > > Do you know how to back up all the DTS packages automatically without
> > > having to put the server name inside the VBscript?
> > >
> > > Thanks in advance
> > >
> > > BIBIBO
> >
> > Not sure if this will help you, but I never use the real server name in
a
> > script
> > or DTS package. I always use an alias name (CName). In fact, I do it
at
> > the
> > level of the database. With this approach, I can move a db and its
> > associated
> > scripts and packages to a different machine and everything continues to
> > work.
> > All I have to do is change the DNS entry to point to the new machine.
> > This
> > works for SQL Server, mapped drives, client ODBC connections, etc.
> >
> > For example, I recently moved my company's data warehouse database to a
> > new,
> > faster server. All apps referred to "DWprod" as the server name, which
> > was
> > really an alias. After moving the db, we changed the DNS entry for
> > "DWprod"
> > and everthing worked fine.
> >
> > You can also add an entry in the HOSTS file on the machine where your
> > script is
> > running to point to the target server. By changing the HOSTS file entry
> > every
> > time you run the script, you can run the same script and have it operate
> > on
> > different servers. You should run ipconfig/flushdns to clear the cache
> > after
> > you change HOSTS. Remember to remove the HOSTS file entry when you are
> > done.
> >
> > HTH
> >
> > Ed
>

"Michael Vardinghus" <michaelvardinghus@hotmail.com> wrote in message
news:michaelvardinghus@hotmail.com:
> Do you have an example of setting it internally ?
>
> is it active x + parameter + connection
>
> "Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
> news:umJM7kEGFHA.1932@TK2MSFTNGP14.phx.gbl...
> > Nice trick
> >
> > You can also create an alias using cliconfg and use the same way.
> >
> > As for the original post of can you move and change in one go then the
> > answer is no.
> >
> > Ideally things like Servername should be as has been mentioned i.e.
> > controlled outside of the package or you should set the package up to
> > look somewhere to fond the server names and then set internally.
> >
> >
> >
> >
> > "eenstrom@optonline.net" <eenstrom@optonline.net> wrote in message
> > news:eenstrom@optonline.net:
> > > eleftheriak@hotmail.com wrote:
> > > > Do you know how to back up all the DTS packages automatically
> > > > without
> > > > having to put the server name inside the VBscript?
> > > >
> > > > Thanks in advance
> > > >
> > > > BIBIBO
> > >
> > > Not sure if this will help you, but I never use the real server name
> > > in
> a
> > > script
> > > or DTS package. I always use an alias name (CName). In fact, I do
> > > it
> at
> > > the
> > > level of the database. With this approach, I can move a db and its
> > > associated
> > > scripts and packages to a different machine and everything continues
> > > to
> > > work.
> > > All I have to do is change the DNS entry to point to the new
> > > machine.
> > > This
> > > works for SQL Server, mapped drives, client ODBC connections, etc.
> > >
> > > For example, I recently moved my company's data warehouse database to
> > > a
> > > new,
> > > faster server. All apps referred to "DWprod" as the server name,
> > > which
> > > was
> > > really an alias. After moving the db, we changed the DNS entry for
> > > "DWprod"
> > > and everthing worked fine.
> > >
> > > You can also add an entry in the HOSTS file on the machine where
> > > your
> > > script is
> > > running to point to the target server. By changing the HOSTS file
> > > entry
> > > every
> > > time you run the script, you can run the same script and have it
> > > operate
> > > on
> > > different servers. You should run ipconfig/flushdns to clear the
> > > cache
> > > after
> > > you change HOSTS. Remember to remove the HOSTS file entry when you
> > > are
> > > done.
> > >
> > > HTH
> > >
> > > Ed
> >