I am planning on speaking soon... just need to get some demo scripts and some stuff set up.
I am hoping to do a presentation on troubleshooting service broker. I've had to do some weird troubleshooting at work, so was thinking it would be a fun topic to cover.
Things like message poisoning when using triggers on a message logging table and messaging from SQL 2016 to an older version (encryption is different by default so if you don't specify the encryption, the message can look like it sent from the sender but never arrive) and things like that. Start by showing "this is the thing that is happening", get suggestions from the group about how to solve it (the local group is pretty small, so participation shouldn't impact timing too badly) and then show them how I would troubleshoot it. Doesn't mean my method is the best way; MOST of the time, I troubleshoot service broker by re-sending the failed message with profiler attached to watch what is going on, but it does depend on the problem... poison messages I don't do that as it wouln't be that helpful.
the first step is to get service broker running on 2 different SQL instances on my laptop. That thing is not very powerful (2 GB of RAM :/) so I'm hoping I don't kill the poor little thing. But get SQL up with 2 versions (2012 and 2016), then get service broker up and running, then get scripts to break and repair it.
The big thing with it is that I will not be presenting it as a "best practice" by any means. I am no expert in service broker.
Nice thing is I am the local chapter leader, so if I am not ready to present, it is all on me to get a different thing ready. And I try to have a backup plan figured out before I have to present. Heck, I bring 2 projectors to each meeting just in case one fails and I have the presentation we are going over on USB key in case my laptop decides to not cooperate.