There used to be a list published yearly of most popular node names. Whatever happened to that? I seem to recall Star Trek names topping the list.

Someone named a bunch of the servers and user ID's I deal with now including a reference to the city or site they were in when they were created. Bad idea, they are in a different city now. Some moved to a different city that existed in the org at that time, too. With a virtualization project going on, it's even worse…

I once put in one of my kids' baby pictures on an employee id portal I was demoing. That got a big smile from everyone. But they wound up getting a different system.

And yes, you should make sure scott's locked down, per @jpiwowar's comment on its being a common attack vector.

“Dude, lambert58 and stallworth82 need more memory.”

You made my point about conference naming, which I'm sure lots of unknowing Oracle corporate types hit when they started going to Pleasanton looking for the Moonraker conference room.

What has two fingers and loves the “DBA nerd/science fiction dork commentary”? This guy. Have we met?

I like theme names better, but they are confusing if you're going to a new place, e.g. PSFT old HQ.

Corporate probably has a hundred or so conference rooms, so naming them might get to be a chore, to my point about creativity having a lifespan.

+1 for beer-themed conference rooms.

Naming is fun, unless you have to do it frequently, which is the problem with demo data. Like I said, my creative juices usually run out after a couple records, then it's just another chore of testing.

A couple of years ago, our building initiated a contest to rename our meeting rooms (which have wonderful names such as “Engineering Conference Room 2″). Since our building was (at the time) exclusively involved in fingerprint identification technology, a couple of us were pushing the idea of naming the rooms after some of the pioneers of fingerprint identification – the Vucetich room, the Henry room, and so forth. Unfortunately, the rooms today have names such as…”Engineering Conference Room 2.” (OK, there is a “Newport Beach room,” but it's a windowless closet.)

Our experience shows that you're never going to get a consensus on dummy naming, because people have different experiences – the Family Guy fan and the 1961 Yankees fan aren't going to find common ground. Things work best if you give a single person dictatorial power over the naming structure. When I have such power, I gravitate toward U.S. presidents, co-workers, and random cities with various levels of meaningfulness (Espoo, Schmelz, Aarau, Guasti, Gresham…).

But the next time that I'm entering a fake criminal record at a trade show demonstration booth, I promise to try to remember to use “Kuramoto” as the last name on the fake criminal record. You're welcome.

I've always been partial to retired Hispanic baseball players…don't know why, they just always seem to come to mind. Luis/Tiant, Orlando/Cepeda, Julian/Javier, Cesar/Geronimo, Davey/Conception…can't wait for Coco Crisp to retire

scott and his cat still exist in the example schemas, if installed, though the account is typically expired and locked during installation, since it's a common attack vector.

I've always gravitated toward Babylon 5 characters as my server-naming convention, because the names tend to be short. Of course, the trend nowadays seems to be dry, boring numbering schemes. Probably all for the best; with the number of servers people have to manage these days, one would probably get into pretty obscure territory in the chosen namespace (“that machine? Oh yeah, the green dude from Season 8, Episode 12, right.”).

*ahem* Yeah, I'm sure that's just the sort of DBA nerd/science fiction dork commentary you were looking for to enrich this conversation.

I know it seems soulless, but I've always preferred a numeric scheme, consistent from floor to floor, for labeling meeting rooms. Easier to map if I'm headed to unfamiliar territory.

By the way, that's a good interesting about “scott”, but i have to lock or drop him from my database.

system manager intitle:postmortem inauthor:cornwell