We're having to install new SQL servers on a new naming convention. We
know the changes we have to make on the applications that hit the SQL boxes.

However, we are not sure what DTS or SQL Agent jobs would need to be
changed.

Is there a way that we can search the DTS & SQL Agent jobs for a literal
that would refer to our old SQL server name and could identify & change
it to run on the new one?

Or,

is there a way to pass a parameter into the DTS or the Agent jobs that
would point them to the new server?

We're running Windows 2000, SQL 2000. We'll be moving to Windows 2003
and SQL 2000.

Any ideas appreciated.

Thanks,

BC

Hello Blasting,

I am not sure which part it is that you want to replace. it is the server
connections inside the package or is it the server parameter to DTSRun that
tells it which server to retrieve the package from.

The latter you are looking for the /A switch

The former is a little more difficult unless you have planned for it. Ideally
you would use something like the Dynamic Properties task to be able to set
the connection properties at runtime. Another way is to set them in code
in the package to be based on Global Variables and you pass the value of
the GVinto the package from DTSRun using the /A switch




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

For the agent jobs, you can script them out and search through the SQL that
is created. For DTS, you could probably save it as a VB file and search
through that.

Hope this helps!

--
Chuck Heinzelman
MCSD, MCDBA

I support the Professional Association for SQL Server (www.sqlpass.org)

This posting is not an endoresment of any product.
Information is provided as-is, and carries no warranties - either express or
implied.

Please respond in newsgroups only.

"Blasting Cap" <goober (AT) christian (DOT) net> wrote