5 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link

Both DBA.SE and Stack OverflowStack Overflow suffer from a similar problem, when users post sql related questions there is a tendency to solely tag the question with but exclude the RDBMS.

This is great if they are looking for an ANSI standard answer but more times than not, they want an answer for a specific database product. Since they've left off the RDBMS, this leads to comments and/or answers which guess the possible solution, and frustration for users.

I've seen this DBA Meta post and it says it should be used:

when the question has a direct relation with SQL.

But that's pretty much ever question here. It seems like this is far too broad of a tag especially if the users don't include the RDBMS they are targeting.

So my question is, does the make sense here on DBA? Should the tag be removed?

Both DBA.SE and Stack Overflow suffer from a similar problem, when users post sql related questions there is a tendency to solely tag the question with but exclude the RDBMS.

This is great if they are looking for an ANSI standard answer but more times than not, they want an answer for a specific database product. Since they've left off the RDBMS, this leads to comments and/or answers which guess the possible solution, and frustration for users.

I've seen this DBA Meta post and it says it should be used:

when the question has a direct relation with SQL.

But that's pretty much ever question here. It seems like this is far too broad of a tag especially if the users don't include the RDBMS they are targeting.

So my question is, does the make sense here on DBA? Should the tag be removed?

Both DBA.SE and Stack Overflow suffer from a similar problem, when users post sql related questions there is a tendency to solely tag the question with but exclude the RDBMS.

This is great if they are looking for an ANSI standard answer but more times than not, they want an answer for a specific database product. Since they've left off the RDBMS, this leads to comments and/or answers which guess the possible solution, and frustration for users.

I've seen this DBA Meta post and it says it should be used:

when the question has a direct relation with SQL.

But that's pretty much ever question here. It seems like this is far too broad of a tag especially if the users don't include the RDBMS they are targeting.

So my question is, does the make sense here on DBA? Should the tag be removed?

4 replaced http://meta.dba.stackexchange.com/ with https://dba.meta.stackexchange.com/
source | link

Both DBA.SE and Stack Overflow suffer from a similar problem, when users post sql related questions there is a tendency to solely tag the question with but exclude the RDBMS.

This is great if they are looking for an ANSI standard answer but more times than not, they want an answer for a specific database product. Since they've left off the RDBMS, this leads to comments and/or answers which guess the possible solution, and frustration for users.

I've seen this DBA Metaseen this DBA Meta post and it says it should be used:

when the question has a direct relation with SQL.

But that's pretty much ever question here. It seems like this is far too broad of a tag especially if the users don't include the RDBMS they are targeting.

So my question is, does the make sense here on DBA? Should the tag be removed?

Both DBA.SE and Stack Overflow suffer from a similar problem, when users post sql related questions there is a tendency to solely tag the question with but exclude the RDBMS.

This is great if they are looking for an ANSI standard answer but more times than not, they want an answer for a specific database product. Since they've left off the RDBMS, this leads to comments and/or answers which guess the possible solution, and frustration for users.

I've seen this DBA Meta post and it says it should be used:

when the question has a direct relation with SQL.

But that's pretty much ever question here. It seems like this is far too broad of a tag especially if the users don't include the RDBMS they are targeting.

So my question is, does the make sense here on DBA? Should the tag be removed?

Both DBA.SE and Stack Overflow suffer from a similar problem, when users post sql related questions there is a tendency to solely tag the question with but exclude the RDBMS.

This is great if they are looking for an ANSI standard answer but more times than not, they want an answer for a specific database product. Since they've left off the RDBMS, this leads to comments and/or answers which guess the possible solution, and frustration for users.

I've seen this DBA Meta post and it says it should be used:

when the question has a direct relation with SQL.

But that's pretty much ever question here. It seems like this is far too broad of a tag especially if the users don't include the RDBMS they are targeting.

So my question is, does the make sense here on DBA? Should the tag be removed?

3 edited tags
| link
    Tweeted twitter.com/#!/StackDBAs/status/604429975874375680
2 added 243 characters in body
source | link
1
source | link