3

For instance, referring to DB2 for Linux, Unix, or Windows as opposed to just ?

Also, when approving tag wiki edits, it would be great to be able to see proposed edits made against both the excerpt as well as the main body in a single review task... I just rejected a tag body edit for because it didn't explain what luw was; however the very next review task was for the excerpt of which did explain what luw was. If I would have been able to see the excerpt with the body, or at least the excerpt first, I would have approved the edit.

  • 1
    As a general rule, I would say no but my understanding for DB2 is that there is an a difference in capabilities and administration for luw vs zOS – billinkc Nov 13 '13 at 19:21
  • If we ever did agree the need for this sort of tag, it'd be in addition to the base RDBWS tag rather than an alternative to it of course, is that what you meant? – Jack Douglas Dec 29 '13 at 15:18
  • Precisely, @JackDouglas - I was wondering if it is necessary to have multiple tags for a single piece of tech. I guess in this particular case, I would lean towards having a single tag, and tagging the question with whatever O/S tag is appropriate if the O/S makes a huge difference to the question or answer. – Max Vernon Dec 30 '13 at 21:01
  • 1
    Although, having said that, I can now see this is similar to the situation with sql-server and sql-server-2012 (ie, various versions of a piece of tech have their own tag already). – Max Vernon Dec 30 '13 at 21:02
  • 1
    Yup, that is the analogy I had in mind too, though dbcc is not sql-server-dbcc – Jack Douglas Dec 30 '13 at 21:11
7

Always remember that tags are intended to make it easier to find a question, not to find the most Type-A classification of questions. You get 5 of them. I expect it would be easier to just tag with the OS involved if you need to narrow it down.

  • 1
    Nice succinct answer - that's why you're such a great mod! – Max Vernon Nov 13 '13 at 21:18
  • 1
    Thanks, felt a little snarky >.< – jcolebrand Nov 13 '13 at 21:55
4

In the case of MySQL, some features taken for granted in Linux are not available in Windows.

The first thing that came to mind was the option innodb_flush_method. In Linux, it allows InnoDB to bypass caching to the OS and explicit caches to the system tablespace. That feature is not available in the Windows version (since Windows will cache in the OS against your will).

Recently, someone asked a question involving mysqldump in Windows. The word windows was not highlighted or overly emphasized. It was not even tagged as windows. (I added the tag later). I answered the question based on seeing that word 'windows'. Had I not seen the word 'windows', I would have answered in terms of Linux shell scripting instead of Windows batch commands.

SQL Server obviously does not need a windows tag since it is a Window product.

PostgreSQL and Oracle have versions available for Windows.

Answers based on OS platform have a bearing on

  • How much memory can be allocated
  • What kind of disk layouts are feasible
  • How the OS caches disk changes

Tags for the OS make sense. A tag should not have the product and OS combined as a single token. If a posted question has a product and the question is something that is specific to the product but agnostic to the OS, an OS tag should not be used.

You must log in to answer this question.

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