General discussion

Locked

Why not to rename a server

By TranMan ·
The place I work (Kansas Dept of Transportation) has a policy of renaming servers every time they are replaced (I'm talking about the box, not software). This causes no end of headaches because every program that references the server, every ODBC DSN, every linked table; etc has to be fixed. I maintain that this is a stupid policy. 500 points for a lucid description of why this is stupid, or links to a couple of sites that would say this is a stupid thing to do. I want something I can take to management to convince them to stop this. Can there actually be any reason you would want to rename a production server???

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Why not to rename a server

by Bob Sellman In reply to Why not to rename a serve ...

Try this:

Currently every new server is assigned a new name. This was an effective system in the past because it was time consuming to move applications currently in use (production) to a new. Compatibility with changes in server software on the new servers was also a problem.

Times have changed. Compatibility is not the problem it was in the past. Transfer of applications and data to a new server can be accomplished much more quickly than was possible in the past.

While transfer of applications and data to the new server can be accomplished more quickly, reducing down time to a minimum, the greater use of networked applications and databases has elevated what was previously an annoyance to a major problem.

We now work in an environment where there are many users of each application and the users may not be all located in one centralized area of a building. In fact, they can be in locations physically separated by many miles.

The current policy of assigning a new name to the replacement server, rather than using the same name as the server it replaces, has now become a major problembecause of this combination of greatly increased numbers of users and users who are diversely located.

Most applications and related software include links that reference the server name. With more applications, more users, and more diversely located users, fixing these references for everyone and every application becomes a daunting, time consuming process. It is prone tocause expensive delays and other costly problems when users try to use applications on the replacement server.

Change this policy so that the replacement server will be assigned the same name as the server it replaces. This will eliminate the costs of loss of productivity, sales, and customer relations due to problems caused by the current policy of assigning a new name to the replacement server.

Collapse -

Why not to rename a server

by TranMan In reply to Why not to rename a serve ...

Poster rated this answer

Collapse -

Why not to rename a server

by Don Christner In reply to Why not to rename a serve ...

I can't think of a valid reason to change the name of the server just because it's being replaced.

Try documenting the amount of time that it takes to find and fix all of the program referances, etc. Then put a dollar amount on the number of hours it takes just because of the renaming. Once they see a dollar amount on the policy they may rethink their idea.

Don

Collapse -

Why not to rename a server

by TranMan In reply to Why not to rename a serve ...

The problem is that I work for state government. They do not give a rat's a** if a policy is wasteful or stupid. The reason they change the servers' names is, "because they have always changed their names". Go figure.

Collapse -

Why not to rename a server

by chris hirst In reply to Why not to rename a serve ...

I have found the best way of changing any policy that does not work is to show a cost saving. Most directors etc do not read reports and take very little notice of comments made. but show the how much more bonus they may make and you don't have timeto draw breath before your policy becomes company policy.

Collapse -

Why not to rename a server

by TranMan In reply to Why not to rename a serve ...

I work for state government. These idiots get their bonuses, no matter what stupid and wasteful things they do.

Collapse -

Why not to rename a server

by TranMan In reply to Why not to rename a serve ...

This question was closed by the author

Back to Networks Forum
7 total posts (Page 1 of 1)  

Related Forums