We're having to move SQL to a new server, which must be a new name.

Previously, I had been using an old name, and when the server was
replaced, we just gave the new one the old one's IP and name when we
brought it online.

Is there a way though, for me to make DTS and jobs in SQL "portable"
(for lack of a better word), rather than having to change each & every
DTS job on the server to point to the new server? In my jobs I also
copy tables from one server to another, etc. And on a secondary server,
it refers a number of things back to the first server, by name.

Is there some sort of parameter I can pass to the DTS or Agent jobs to
make it point to the new server, or am I just Out of Luck on being able
to NOT have to change all my DTS's each time we replace one of our servers?

BC

Blasting Cap wrote:
You can create a UDL file (Microsoft Data Link) connection in the
package. That way you only have to change the connection details in the
one file.

Or you can add a Dynamic Properties task that sets up the connection
based on a config file or environment variable or global variable.

Or you can use an ActiveX script task to set the connection data
source.

--
David Portas, SQL Server MVP

Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.

SQL Server Books Online:
http://msdn2.microsoft.com/library/m...S,SQL.90).aspx
--

David Portas wrote:

In client n/w utility add alias as old machine name for your new
machine name

Regards
Amish Shah