Hi,
I have a situation I hope the smart people
on here can help me with.
We have a local SQL server that is moving to
the SAAS (online) environment. In this new environment, the owners of this SQL
DB will rename the server, the SQL name and the SQL instance name to their
naming standard.
The problem is we have about 20 custom programs that
point to our existing SQL server (with existing name). Not to mention dozens of
SSIS packages, procs, views, etc. When we move our server to the SAAS
environment they will be renaming the server, instance, etc. so- none of our
programs will connect.
Is there a way we can use alias names for:
1)
The Server (host file? - dns redirect?)
2) The SQL server name
3) The SQL
instance name
Or is there some other way that we don't have to re-write
all of our programs/packages?
I have a situation I hope the smart people
on here can help me with.
We have a local SQL server that is moving to
the SAAS (online) environment. In this new environment, the owners of this SQL
DB will rename the server, the SQL name and the SQL instance name to their
naming standard.
The problem is we have about 20 custom programs that
point to our existing SQL server (with existing name). Not to mention dozens of
SSIS packages, procs, views, etc. When we move our server to the SAAS
environment they will be renaming the server, instance, etc. so- none of our
programs will connect.
Is there a way we can use alias names for:
1)
The Server (host file? - dns redirect?)
2) The SQL server name
3) The SQL
instance name
Or is there some other way that we don't have to re-write
all of our programs/packages?
qeqw