Sage 100

Back in the on-premise days, it made sense to have the location, branch, function, etc in the name, but in these cloud-y times where servers are treated like cattle instead of pets, naming structure doesn't seem to matter as much.  I still remember our one customer whose sysadmin insisted on naming the servers after Lord of the Rings characters.  If you're curious, ELROND was the Sage server....

------------------------------
Steve Iwanowski, NextStep Technology Advisors, aka DSD Lancaster PA ¯\_(ツ)_/¯
------------------------------

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.

I bet @Beth Bowers will vote for Disney characters.....

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

I bet @Beth Bowers will vote for Disney characters.....

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.

I have a client who uses planet names for workstations.

I bet @Beth Bowers will vote for Disney characters.....

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.

I have a client who uses planet names for workstations.

I bet @Beth Bowers will vote for Disney characters.....

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.

I have a client who uses planet names for workstations.

I bet @Beth Bowers will vote for Disney characters.....

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.

@Barbara Goldstein  This gives a double meaning to the question "... and what planet are you on?".  

I have a client who uses planet names for workstations.

I bet @Beth Bowers will vote for Disney characters.....

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.

I bet @Beth Bowers will vote for Disney characters.....

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.

Confuse the heck out of everyone and name them after Quasars:

 Psc 14.78, Col 14.62v, 1101+384 Mrk 421, 1133+704 Mrk 180, J0005-0006, J0303-0019, QSO J0313−1806, and J0529-4351. Looks super techie!

I bet @Beth Bowers will vote for Disney characters.....

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.

Ooh, no thank you!

Confuse the heck out of everyone and name them after Quasars:

 Psc 14.78, Col 14.62v, 1101+384 Mrk 421, 1133+704 Mrk 180, J0005-0006, J0303-0019, QSO J0313−1806, and J0529-4351. Looks super techie!

I bet @Beth Bowers will vote for Disney characters.....

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.

The Big Bang folks at the Jet Propulsion Laboratory understand that line of thought perfectly..

My server is BLS007, a shout out to James, James Bond!

Ooh, no thank you!

Confuse the heck out of everyone and name them after Quasars:

 Psc 14.78, Col 14.62v, 1101+384 Mrk 421, 1133+704 Mrk 180, J0005-0006, J0303-0019, QSO J0313−1806, and J0529-4351. Looks super techie!

I bet @Beth Bowers will vote for Disney characters.....

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.

I am happy with any naming convention as long as there IS one. I have one site where the "IT" guy leaves the default Dell assigned name! Try remembering your install is on DH4W92L.

The Big Bang folks at the Jet Propulsion Laboratory understand that line of thought perfectly..

My server is BLS007, a shout out to James, James Bond!

Ooh, no thank you!

Confuse the heck out of everyone and name them after Quasars:

 Psc 14.78, Col 14.62v, 1101+384 Mrk 421, 1133+704 Mrk 180, J0005-0006, J0303-0019, QSO J0313−1806, and J0529-4351. Looks super techie!

I bet @Beth Bowers will vote for Disney characters.....

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.

I bet @Beth Bowers will vote for Disney characters.....

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.

In a former life, our servers were named after Muppets. I was the official Muppet researcher who had to come up with a list of prospective Muppet names for each new server and locate pictures that could be taped on the front of each server.

I bet @Beth Bowers will vote for Disney characters.....

Server names can be like naming your children, being creative in naming them.  When a non-Sage hosting IT company names things, they tend to not care so much about any naming conventions and name them whatever.  I don't like having to tell them how they should name things, but when they come up with Sage, Sage100, Sage2k for their previous namings, none of them are very logical.  In fact, this particular IT company was trying to school me last upgrade that Sage100 isn't Sage100 any more - it's called Sage.  Hah - not!  Anyway, since they have gone the boring route of their previous namings, I told them what to name this server this time around.  Would have been more fun to name them after mountains, Disney characters or galaxies ... anything goes I guess.

Thanks all!

What I see the most with server naming is something basic like SAGE-01 or SAGE-02. Usually nothing fancy. M

My biggest takeaway is the importance of keeping great notes. I have seen more and more clients/prospects/suspects with no sense of urgency whatsoever --- until suddenly they do have some urge to upgrade or green light a project they spoke to you about 18 months ago. This is when it REALLY pays to have good notes and documentation.