14

One of the proposals I had committed to, Database is now known as Database Administrators. Why is this so ? Now I fear that the Stack Exchange site is catered more towards Database Administrators than Database Professionals as to which I had committed.

(yes, there is a huge difference between database professional and a database administrator).

8
  • 6
    Thanks for this question. It gave me chance to uncommit before the site went into private beta. While I might find the site useful as an occasional user, I'm nowhere near the target audience any more.
    – ChrisF Mod
    Commented Dec 20, 2010 at 9:31
  • @ChrisF I know, I'm in the same boat. Commented Dec 20, 2010 at 13:11
  • 1
    @ChrisF Don't you have a choice to make it suit your preferred audience? What's preventing you from asking the questions you intended to ask?
    – Ivo Flipse
    Commented Dec 20, 2010 at 13:46
  • 2
    @Ivo - I would find it difficult to ask dba type questions, but would benefit from reading existing questions and answers. I can see that I'd use the site at some point but I can't commit to the level of site use that comes with "commitment".
    – ChrisF Mod
    Commented Dec 20, 2010 at 13:50
  • No @ChrisF I meant, why don't you ask database professional questions? If the site is meant to be for professionals and administrators, why no use it the way you think it should be used?
    – Ivo Flipse
    Commented Dec 20, 2010 at 13:59
  • 1
    @Ivo - I won't have enough of those questions to warrant spending a commitment token. I would hope my questions would be professional (as they would be for my work), but I'm a developer not a dba.
    – ChrisF Mod
    Commented Dec 20, 2010 at 15:51
  • @Ivo - Database questions are more like what's wrong with this join ? Are my indexes working ? Why isn't this index picking up. DBA questions are more like HOW can I replication, my database crashed, how can I recover ? How can I upgrade my database. With a site titled "Administration" the focus is more narrow. Wikipedia may say They are also known by the titles Database Coordinator or Database Programmer, and is closely related to the Database Analyst, Database Modeler, Programmer Analyst, and Systems Manager - but in practice DBA's tend towards maintenance more. (IME). Commented Dec 20, 2010 at 16:00
  • Perhaps you simply shouldn't agree with the current practice and follow Wikipedia's example instead. Just a matter of perspective @Sathya
    – Ivo Flipse
    Commented Dec 20, 2010 at 16:04

3 Answers 3

12

"Databases" is nebulous term, used by many, many professional disciplines. So we had to become absolutely crystal clear about the primary audience for this site. Yes, a clearer title could have be chosen early on to indicate the target audience… preferably by the community creating the proposal — Or we can step in and take one of the following three actions.

Pick one:

  1. Leave it as a "Database" site whose primary audience becomes professional programmers whose skill set includes slinging around the occasional SQL code to get their job done.
    Result: Closed as a duplicate of Stack Overflow
  2. Leave it as a "Database" site whose primary audience becomes system administrators who might have a database or two to maintain as part of their organization.
    Result: Closed as a duplicate of Server Fault
  3. Create a "Database Administrator" site for professionals who properly call themselves "DBAs" as a full-time profession; Those who identify themselves as neither programmers nor system administrators and don't currently feel they have a place on our network.
    Result: Rename "databases" to DBAs before launch… instead leaving the target audience to chance having to close it down when 70-80% of the content duplicates existing sites.

So we went for option #3.

4
  • 2
    +1 I like option 3. Option 3 makes me feel warm and fuzzy inside. Option three shaves my beard, slices, dices, and makes julienne fries! I'd pay $19.99 plus s+h for option 3, plus get a second option 3 for free (just pay separate shipping and handling). Also, I think I need sleep! Commented Dec 21, 2010 at 16:15
  • 1
    I agree that Stack Overflow is the current location to post database programming questions. But the SO fac doesn't say a singe word about database programming. And I would prefer to have a seperate site, where I'm not forced to ignore all the regular programming questions.
    – bernd_k
    Commented Dec 24, 2010 at 11:31
  • 4. Shutdown the proposal and start over with a clear definition: "Database Administrators" and not "Questions about database". I feel just like ChrisF
    – BrunoLM
    Commented Jan 6, 2011 at 23:39
  • Why not just "Database Professionals"
    – Anoplexian
    Commented Apr 28, 2016 at 17:24
7

yes, there is a huge difference between database professional and a database administrator

Er.. what?

All our sites (at least in theory) cater to experts, and we felt the best way to make that clear is to say DBA, as in the standard professional title:

http://en.wikipedia.org/wiki/Database_administrator

A database administrator (DBA) is a person responsible for the design, implementation, maintenance and repair of an organization's database. They are also known by the titles Database Coordinator or Database Programmer, and is closely related to the Database Analyst, Database Modeler, Programmer Analyst, and Systems Manager. The role includes the development and design of database strategies, monitoring and improving database performance and capacity, and planning for future expansion requirements. They may also plan, co-ordinate and implement security measures to safeguard the database.[1] Employing organizations may require that a database administrator have a certification or degree for database systems (for example, the Microsoft Certified Database Administrator).

And, this is hilarious

It has been suggested that this article or section be merged into Database.

I lol'ed! We had the same discussion, but I think when you're trying to build a community of experts it's best to spell that out as clearly as possible in the title and description.

Should we have figured this out earlier? Sure. But at least we figured it out before the site went into private beta and people got confused about who the expert audience is for this site.

8
  • 3
    There was initial discussion about clashing with SO 6 months ago. Why was it NOT renamed then ? Commented Dec 20, 2010 at 12:54
  • 4
    You do realize with the site targeted at DBA's - most of the on-topic/off-topic questions proposed during the definition state are irrelevant ? Lot of commitments were because of site's initial focus at database professionals, not administrators. Commented Dec 20, 2010 at 13:24
  • 1
    @Sathya - you do realize that figuring out this sort of thing is probably one of the very reasons for Area51 in the first place, right? Commented Dec 20, 2010 at 18:31
  • 5
    @Andrew you do realize it was renamed after hitting 100% commitment & all the a51 definitions were in place ? Commented Dec 20, 2010 at 18:43
  • Perhaps those definitions were what caused the rename? (I really don't know, hence the question mark.) Commented Dec 20, 2010 at 20:50
  • 1
    "Should we have figured this out earlier? Sure. But at least we figured it out before the site went into private beta and people got confused about who the expert audience is for this site." Honestly, I think that is the answer to this question, period. Commented Dec 20, 2010 at 20:53
  • which comes back to the comment I first posted - There was initial discussion about clashing with SO 6 months ago. Why was it NOT renamed then. THAT is what I have a problem with. It was known that there might be an overlap - why wasn't action taken then ? @Andrew Commented Dec 21, 2010 at 0:21
  • @Sathya I suspect you are confusing discussion about the topic of the site, and determination on the name of the site. Two separate - though certainly related - things. Commented Dec 21, 2010 at 0:57
3

Probably because the other major type of database professional is the database developer, and I think there's already a site for that, somewhere...

11
  • Took 'em so long ? Commented Dec 20, 2010 at 4:56
  • The meaning of your comment escapes me. It "took them" as long as it took them to make that choice... are you asking why? Commented Dec 20, 2010 at 4:59
  • 1
    @AndrewBarber Well, yes. Kind of irritating to see a proposal you really wanted to happen suddenly on a tangential route. Commented Dec 20, 2010 at 5:03
  • 2
    I think it would be much more irritating to see a proposal which clashed so significantly with an existing site. Wouldn't you agree? Commented Dec 20, 2010 at 5:06
  • 2
    Oh, and it's not at all tangential in the least to properly narrow the focus of an Area51 site so that it does not conflict with an existing site. Commented Dec 20, 2010 at 6:25
  • @AndrewBarber They had 6 months to figure that out. Why now ? Why not earlier ? Commented Dec 20, 2010 at 12:52
  • 3
    @Sathya - I don't know. Why haven't you yet come to understand why the change was made? If you have, why didn't you realize it last night, or a few hours before? Commented Dec 20, 2010 at 18:32
  • @Andrew - The name wasn't "database administrators" when I visited it couple of days ago. Commented Dec 20, 2010 at 18:44
  • I wasn't quibbling on when the decision was made. Commented Dec 20, 2010 at 20:54
  • @ErikE I never asked to have it both ways. Also... you know how old this is, right? Commented Feb 10, 2012 at 22:35
  • Sorry, I do see that. Never mind? I'll delete my comment.
    – ErikE
    Commented Feb 10, 2012 at 22:41

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .