I’ve worked with a lot of features in SQL Server. I know what I think is tricky and more difficult than it looks like at first. But experiences vary, right?
So I asked the Twitterverse, “What are the Top 3 Trickiest Features in SQL Server?” Here’s what I heard back.
SQL Server Replication “wins” the top spot for being mentioned by the most people. Maybe it won because it’s touched the hearts of the most people since it works with Standard Edition. Maybe it’s just been in the product long enough to have tricked lots of us?
@Kendra_Little replication is definitely #1!
— Derik Hammer (@SQLHammer) July 8, 2014
#2: Availability Groups
Coming in second is SQL Server Availability Groups. These may have only been with us since SQL Server 2012, but their complexity has impressed quite a few people already.
@Kendra_Little replication, service broker, AG
— Jason Kyle (@JasonNKyle) July 8, 2014
The number three place goes to a feature I hadn’t thought of myself… database administrators themselves. I laughed out loud when I saw these tweets, but, well, there’s some truth in it. We are a tricksy bunch!
— Joe Fleming (@muad_dba) July 8, 2014
Other top tricky features that came up:
- Service Broker (guessing they worked at MySpace)
- SSIS (oh, the clicking! the clicking!)
- SQL Server Clustering
- Active Directory (ah, Kerberos authentication, you devil you)
- Resource Governor (someone actually used Resource Governor!?!?!)
- Extended Events
- SAN Administrators
- Enterprise Architects
My Personal Top 3
Turns out I’m not so different from the Twitter community. My personal top three trickiest features are: Availability Groups, Replication, and Service Broker. (I’m not really all that into queues in SQL Server, but I do like Event Notifications, which use the Broker framework.)
What are yours?