I want to open a debate on SQL Server Client Network Utility. What are the strong points and limitions using this technique to use database alias.
Let me describe my position.. i am having 2 servers
1 Application Server (named SIRUS)
2 Database Server (named ORION)
i am running hundreds of applications on SIRUS which is using database named ORION. Now what i want to do is to merge both these servers by putting one strong machine instead of 2 to be used as application as well as database server.
Now my problem is if i name new machine as ORION.. then i have to change all the physical paths of hundreds of applications which is practically not possiblem.. and if i name this new machin as SIRUS than i have to chnage database name of my hundreds of application..which is again not possible.. now i m working on possiblity if i name my mahcin as SIRUS and the database name on this machine as ORION..
@ram has given me idea to use SQL Server Client Network Utility to create alias of database SIRUS with the name of ORION on the machine named SIRUS..
Now i want views from experts if i m using this structure, is there any limitations in it ?? i have some 10-12 machines in my network and i can create database alias on each of the machine.. is there a way if i can do sometihng only at server to create alias to be used in the network without doing anything with workstations ??