Which falls over when db01 ain't a database machine anymore.
When I ran a large network, machines didn't physically move very much (at least, far less often than their logical functions changed); we had a naming scheme based on datacenter code, rack ID and rack position:
sjc02-X0501-19
would be the machine in sjc02, rack X05.01, unit 19.
Far more important than the actual scheme you use is consistency. Pick one scheme and stick with it. Easier when you pick the right scheme the first time. :)
That's great for SA's who are working in the racks.
Not so great for SA's that are administering the boxes remotely, devs trying to figure out what machine they are on, or teams trying to troubleshoot an issue.
If a box is no longer a db machine, just rename it to something descriptive.
When I ran a large network, machines didn't physically move very much (at least, far less often than their logical functions changed); we had a naming scheme based on datacenter code, rack ID and rack position:
sjc02-X0501-19
would be the machine in sjc02, rack X05.01, unit 19.
Far more important than the actual scheme you use is consistency. Pick one scheme and stick with it. Easier when you pick the right scheme the first time. :)