I do acknowledge that generally it should be easier to understand what the question is about when the tag shows the full name of a product than when it shows an abbreviation.
However, in my view that argument's weight is lessened in this specific case by the fact that the SSMS abbreviation is fairly well-known in the SQL Server world. And we do show the ...
master is a bad tag so we should remove it.
For replication, the following new tags might be good replacements (with the appropriate usage guidance for each):
For the SQL Server system database usage, perhaps master-system-database.
I'm much less convinced that last tag would be ...
It is worth having sql-server-management-studio but it should be a synonym of ssms as management-studio currently is.
Result: ssms would remain the display tag, but tag search etc. would match the longer forms.
Given that every single question that is tagged postgres-performance will also be tagged postgres, the only gain in having a separate postgres-performance tag is the ability to have a customized tag wiki.
The tag wiki itself is great, and especially in this middle paragraph, there is significant Postgres-specific advice:
Consider the basic advice on ...
No action needed
Benefits of the status quo
The postgresql-performance tag is relatively popular (253 questions)
It is actively curated and promoted by its subject area experts both here and on SO
The tag Excerpt and Wiki are (unusually!) useful, appropriate, and targeted to the intended usage
This tag therefore adds value to the community in the practical ...
I think discussing / tuning / optimizing performance is sufficiently distinct for the various RDBMS to warrant a separate tag. We have put some thought into refining information, instructions and resources in postgresql-performance and it serves well so far. (I say "we" because it started with the related tag on SO.)
If general performance aspects are ...
I disagree on removing pgadmin tag / renaming to pgadmin-3 - but not strongly on adding it to old questions that apply.
With only 160 questions tagged pgadmin, I don't see any benefit on renaming.
PgAdmin 4 is a total rewrite.
PgAdmin 4 is a total rewrite, yes. But do we really care if the program is written in C or Python? The functionality is very ...
Well, pgadmin-1.18 is definitely useless (it refers to a specific pgAdmin III version).
At the same time, pgAdmin III and pgAdmin 4 are two very different products. If the question is tagged rightly with pgadmin, it completely makes sense to indicate which one it is about. That the users don't use these is not the tags' fault :)
I like where your head is at. I would rather not break down performance by database, just use multiple tags. I'm not sure how to find all the synonyms for everything (ex: slow-log) so I would need help identifying more synonyms
So, here's a thing: I went ahead and did this thinking "yeah, this is a good idea, let's keep things simple! YAY!" and wasn't ...
Since there are only 13 questions linked to the big-table tag, it's likely easier to simply create bigtable and edit the existing questions to use the new tag. Any tag that is unused will eventually be automatically removed by the StackExchange system.
Merging the two is obviously a good idea.
I only ever pick a plural word for tags if the matter itself deals with multiple instances on principal. Here, it should be just trigger. The appended s for the plural is noise, carrying no additional information. Just my opinion ...
The new version tags should be merged.
pgadmin - 157 questions and 9 followers
pgadmin-1.18 - 5 questions and 0 followers
pgadmin-3 - 2 questions and 0 followers
pgadmin-4 - 6 questions and 0 followers
There is no need for pgadmin-1.18, pgadmin-3, or pgadmin-4.
The single tag pgadmin serves to connect subject area experts to ...
This makes sense. We should do this (with ssms as a synonym), at least as a trial.
The rename could be easily reversed if any of the anticipated drawbacks actually materialize.
Our tags are inconsistently expanded - mostly due to the historical tag length limitation e.g. erd
That said, the question is not about whether all acronyms should be expanded or ...
I originally created hierarchical as a target for two synonyms containing the word hierarchical.
On reflection, hierarchy would have been a better name, so I have renamed it as requested.
updating post history, 133 rows affected
updating posts, 113 rows affected
removing/renaming old tag, 1 rows affected
tag remapping of [hierarchy] and [hierarchical] ...