When I hosted this past TSQL-Tuesday, I fully expected to have the wrap-up done a few days later. Lots of personal things interfered, and I’m just getting to it now. Sorry for the delay.
I asked for the topic to be on:
Tell me about a time when you ran up against your own brick wall, and how you worked it out or dealt with it.
We had 17 folks take this topic and run with it. As a teaser, my favorite line in all of these is:
My feeling is that if you’re not hitting brick walls you’re probably not pushing yourself or SQL Server hard enough!
In roughly the order posted, we have:
- Luke Campbell’s (blog | twitter) brick wall is Adding multiple SSISDBs to an AG.
- Steve Jones (blog | twitter) blogged about The brick wall that might still be there…
- Duncan Greaves’ (blog | twitter) brick wall had a simple solution: communication.
- Bert Wagner (blog | twitter) blogged about how reading the documentation for a feature proved to be the key is solving this brick wall.
- Shane O’Neil’s (blog | twitter) brick wall is working with developers and their loop-based method of getting data from SQL Server. What could possibly be wrong with that?
- Kevin Hill (blog | twitter) blogs about people being his brick wall. He uses a bulldozer to get rid of them.
- Rob Farley’s (blog | twitter) brick wall is a different methodology for doing presentations. He may not think he’s brave, but I sure do!
- Stuart Moore’s (blog | twitter) first two brick walls were creating the business case to use SQL Server, and learning how it’s different from Access.
- Hugo Kornelis’ (blog | twitter) blogs about how distractions and plain old hard work help him solve his brick walls.
- Glenda Gable (blog | twitter) talks about how communicating with her accountability partner has kept her on track (but is she still at the wall?)
Hey Glenda… did you ever send that email to Grant? (Inquiring minds want to know!)
- Rob Sewell (blog | twitter) sets time limits to work on problems. Bonus: he also talks about how using the Internet helps with your problems (though make sure that “the solution” is from a trusted, viable source that isn’t outdated!).
- Deborah Melkin’s (blog | twitter) brick wall was resolving deadlocks in a system that couldn’t be modified (very much).
- Andy Yun’s (blog | twitter) brick wall was a Kerbosos double-hop issue encountered during a domain change.
- Jeff Mlakar (blog | twitter) blogs about how the biggest brick wall can be… people.
- Nate Johnson’s (blog | twitter) long post is about supporting bureaucratic standards in a RDBMS system when other systems would have been preferred. Reading this makes me wonder if the Graph table capabilities of SQL Server 2017 would have been able to help Nate?
- James (Jim) McGillivray (blog | twitter) posted about several personality traits that are brick walls. All I can say is… run, Forest, run.
- Jon Shaulis (blog | twitter) talks about when YOU are the brick wall.
There we have it… 17 wonderful posts talking about how people handle running in brick walls. Not surprisingly, many of these brick walls involved dealing with people.
The next TSQL-Tuesday topic is set to be released on September 4th. Stay tuned in to find out what the next guest host wants everyone to blog about!