The question has already arisen (imagine that) and at some point we'll need a faq-like to answer this question, but this is not the FAQ on SQL or on DBA.SE and so we'll start here and we'll make a new post later for the FAQ. Bear that in mind when forming and judging answers to this question.
What actually constitutes a SQL question and what constitutes a question that would be better suited for one of the other tags?
I've started by including all the tags currently present here that can be used (AFAIK) in a SQL context because I think to start with and organize thoughts it would be easier to EXCLUDE rather than define what INCLUDES a SQL question. I could be wrong on this. But it's the tack I chose to take. This is my first time on a private beta too ;)
The tag in question:
The platforms/tools we should be able to exclude:
innodb ms-access mssql myisam mysql mysql-5 oracle oracle-11g-r2 oracle11gr2 phpmyadmin postgresql sql-server sql-server-2005 sql-server-2008 sqlite
The tags that are pretty clearly not SQL questions:
app-sec benchmark best-practices bioinformatics biology blogs books career client-server coredata couchdb data-warehouse db2 document-oriented erd erlang etl google-app-engine learning management mariadb migration mnesia model mongodb monitoring mysqldump nosql process proxy-connections puzzles rdbms relational schemaless security slony-i slow-log source-control sphinx storage-engine support tools tree tweek uniprot vendor-support wallet windows
The remaining tags to be discussed:
My thinking is that if it shows up on the bulleted list then it probably doesn't need to have the SQL tag too, or rather it needs to have the tag listed rather than the SQL tag.
Ok, now for feedback