SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Changing Taxonomy


Changing Taxonomy

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (84K reputation)SSC Guru (84K reputation)SSC Guru (84K reputation)SSC Guru (84K reputation)SSC Guru (84K reputation)SSC Guru (84K reputation)SSC Guru (84K reputation)SSC Guru (84K reputation)

Group: Administrators
Points: 84696 Visits: 19224
Comments posted to this topic are about the item Changing Taxonomy

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Dugi
Dugi
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2910 Visits: 3511
Why not to see the forum more simple organized...I agree...not bad idea!?
Wink

============================================================
SELECT YOUR PROBLEM FROM SSC.com WHERE PROBLEM DESCRIPTION =
http://www.sqlservercentral.com/articles/Best+Practices/61537/
Lynn Pettis
Lynn Pettis
SSC Guru
SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)SSC Guru (52K reputation)

Group: General Forum Members
Points: 52742 Visits: 38684
Just using the ideas you have mentioned in your editorial, I see one problem, most posters don't mention what version of SQL Server they are using when asking for help. OP's have posted questions in the SQL Server 2005 forums, get SQL Server 2005 answers, and then complained because they are using SQL Server 2000 and the code provided uses SQL Server 2005 features.

I think there should still be some breakdown between SQL Server 2000 and earlier versions and SQL Server 2005/2008. It is quite possible that many organizations may continue to use at least SQL Server 2000 for several more years as internal systems may not be migrated as long as they continue to provide service to the business. As some would say, why fix something that isn't broken.

My previous employer used Paradox to support remote offices, and the only reason we dropped the system was that Borland was not going to make Paradox Y2K compliant forcing use of that system. The same (or similiar) may happen with existing SQL Server 2000 applications.

Cool
Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Dugi
Dugi
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2910 Visits: 3511
I agree with you Lynn Petis ...but better will be like this:

SQL Server 2000
Administration
General
Backup & Recovery (backup, restore...)
Security and Auditing (logins, users, roles, schemas)
High Availability (Mirroring, Clustering, Log Shipping)
Performance and Tuning
Replication
Development
T-SQL - Any questions on the T-SQL language or code issues
.NET programming - With regards to querying SQL Servrs
SQL CLR - Assemblies

SQL Server 2005
Administration
General
Backup & Recovery (backup, restore...)
Security and Auditing (logins, users, roles, schemas)
High Availability (Mirroring, Clustering, Log Shipping)
Performance and Tuning
Replication
Development
T-SQL - Any questions on the T-SQL language or code issues
.NET programming - With regards to querying SQL Servrs
SQL CLR - Assemblies

SQL Server 2008
Administration
General
Backup & Recovery (backup, restore...)
Security and Auditing (logins, users, roles, schemas)
High Availability (Mirroring, Clustering, Log Shipping)
Performance and Tuning
Replication
Development
T-SQL - Any questions on the T-SQL language or code issues
.NET programming - With regards to querying SQL Servrs
SQL CLR - Assemblies

============================================================
SELECT YOUR PROBLEM FROM SSC.com WHERE PROBLEM DESCRIPTION =
http://www.sqlservercentral.com/articles/Best+Practices/61537/
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (119K reputation)SSC Guru (119K reputation)SSC Guru (119K reputation)SSC Guru (119K reputation)SSC Guru (119K reputation)SSC Guru (119K reputation)SSC Guru (119K reputation)SSC Guru (119K reputation)

Group: General Forum Members
Points: 119098 Visits: 41482
That's a pretty good layout... I like that. Especially when you make them all have the same layout. And, although it hasn't been mentioned, there is no need for a "newbies" section. It just dilutes the subjects.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Steve Jones
Steve Jones
SSC Guru
SSC Guru (84K reputation)SSC Guru (84K reputation)SSC Guru (84K reputation)SSC Guru (84K reputation)SSC Guru (84K reputation)SSC Guru (84K reputation)SSC Guru (84K reputation)SSC Guru (84K reputation)

Group: Administrators
Points: 84696 Visits: 19224
I really don't want to go 2 levels deep, and I really question how complicated things have gotten. Plus, what's a newbie? They don't necessarily know to post there, at least lots don't, and then when do they stop being a newbie?

I'd like to get down to 4-8 forums in each version if we go that way. And then how much of an issue is it if there are posts in the wrong place? We have lots of that now, and the idea would be to reduce this by having less forums.

Is it better to ask the OP for the version or hope they posted in the right spot?

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Dugi
Dugi
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2910 Visits: 3511
Steve I think you need more moderators to clean the posts in wrong sections!

============================================================
SELECT YOUR PROBLEM FROM SSC.com WHERE PROBLEM DESCRIPTION =
http://www.sqlservercentral.com/articles/Best+Practices/61537/
Jeffrey Williams 3188
Jeffrey Williams 3188
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10283 Visits: 10004
I would recommend that you don't get rid of the data corruption forum. It should be one that stands by itself for those cases where someone is really in need of recovering a corrupted databases.

Other than that, I agree with consolidating the groups as much as possible. Even to the point of consolidating the 2005/2008 forums instead of separate forums. Most of the functionality has not changed between the two - and, where a solution exists in 2008 only, the poster providing the solution can easily state that it is only valid in 2008.

Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs

ps.
ps.
SSCarpal Tunnel
SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)SSCarpal Tunnel (4.2K reputation)

Group: General Forum Members
Points: 4175 Visits: 3668
Hmmmm. I dont know if this will be of any use. but what i feel is the structure be divided into two parts. a) Version b) Section.

A combo drop down for Version containing various versions
6.0
6.5
7
2000
2005
2008
with a default value of 2005 as major questions would be from this version at this time. Also, a striking header asking user to select proper version.

Second part contains section as mentioned in the editorial.

Administration
General
Backup and Recovery (backup, restore, detach, attach)
Security and auditing (logins, users, roles, schemas)
High Availability (Mirroring, Clustering, Log Shipping)
Performance and Tuning
Replication

Development
T-SQL - Any questions on the T-SQL language or code issues
.NET programming - With regards to querying SQL Servrs
SQL CLR - Assemblies

Miscellaneous
Anything not about SQL!
Humor
.....
.....


This will keep the page simple so users can scan through available sections quickly and post their queries in the most appropriate section.
This may ask for some major changes in that page and relevent backend but will make it simpler to use..... good for future... The column Forums in the detailed forum section could contain details like..
(2000) Replication, (2008) Backup and Recovery, (7.0) General etc....

Also, I've not taken into consideration another important aspect... ... that is various editions... like standard, enterprise.... I've seen users mentioning the editions if they're using lower editions.... syntaxes are almost same... only there is quantity of features that is different in various editions...



Pradeep Singh
GilaMonster
GilaMonster
SSC Guru
SSC Guru (119K reputation)SSC Guru (119K reputation)SSC Guru (119K reputation)SSC Guru (119K reputation)SSC Guru (119K reputation)SSC Guru (119K reputation)SSC Guru (119K reputation)SSC Guru (119K reputation)

Group: General Forum Members
Points: 119152 Visits: 45554
Jeffrey Williams (12/28/2008)
I would recommend that you don't get rid of the data corruption forum. It should be one that stands by itself for those cases where someone is really in need of recovering a corrupted databases.


Indeed. We're not CSS, but we do get a fair few posts in there. If those were in the general admin, they'd be much, much harder to find and they probably wouldn't get the assistance they currently do.

Even to the point of consolidating the 2005/2008 forums instead of separate forums. Most of the functionality has not changed between the two


I was thinking much the same thing. There aren't that many differences between the two. New features, sure, but most of the existing stuff behaves very similar. It was 2000-2005 that saw a major engine rewrite.

I admit, I don't use the forum home page at all, but maybe something like this would work...

SQL 2005/2008
General admin (for stuff that doesn't belong in any of the more specific admin sections)
Backup/Restore
Replication
Security/auditing
Data corruption
T-SQL
CLR Development
Performance Tuning

SQL 2000/7
General admin
Backup/Restore
Replication
Security
Data corruption
T-SQL
Performance Tuning

Business Intelligence
Analysis Services
Reporting Services
Integration Services
DTS

Design and Strategy (for discussions of the theoretical concepts or planning)
High Availability
Database Design
Relational Theory
Hardware
General Strategies (for stuff that doesn't belong in the more specific forums)

Outside of SQL
Other database platforms (for problems interacting with Oracle, DB2, MySQL, Progress, etc)
SMO/RMO/DMO
Powershell


If you could hide the editorial, QotD and article discussions forums completely (ie make them not browsable via the forum home page) it would reduce the clutter, reduce the size of all the pages (anyone checked to see how many kb the drop down box at the bottom of each page is?) and stop people posting irrelevance stuff in them

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search