Sometimes just getting approval to attend a conference is a challenge, but getting the green light isn't the only thing you should plan for. Sure, you want to learn some things--but a google search can teach you too. In fact this week we are hearing about new features and functionality from the Ignite event--and I am catching all of it in my bunny slippers.
Why attend a conference then?
Conference season is upon us and Steve and I share some thoughts on why we attend conferences and some of the strategies we have used in the past.
The show notes from today's episode can be found at http://sqldatapartners.com/2017/09/28/episode-111-how-do-you-prepare-for-conferences/. Have fun on the SQL Trail!
As you work with other people, you will experience resistance when you suggest changes and want to implement something new. Why is this?
One podcast listener shared an experience where a problem was occurring. The suggested a solution. The idea was rejected. No solution presented itself and the idea was submitted various times. When nothing else was working, the idea was finally implemented.
The suggested change successfully helped the situation. Victory!
Later, another issue arose and a similar suggestion was made. The expectation was the suggestion would be well received; however, this was not the case. The idea was still met with hostile resistance.
Have you faced a situation like this before? Why wasn't there an trust built because of the first recommendation?
Our conversation for today's episode centers around the idea of building trust on the teams you work with. As most our listeners are in the data platform space, we thought it would be a good idea to reach outside our community to folks we might receive the most pushback from--developers. We are happy to have Richard Campbell on the show with us today. Richard is the co-host of the .NET rocks podcast and you might recognize him from one of his many Channel9 videos.
We chat with Richard about how we can build trust and some common ways we attempt to show authority can backfire on us and actually cause more problems. We talk about some of the ways those we trust have gone about earning our trust. I know you enjoy this episode.
The shownotes for today’s episode is found at http://sqldatapartners.com/2017/09/20/episode-110-how-do-i-build-trust-with-my-team/ and have fun on the SQL trail.
In episode 64 we interviewed Patrick Thomas, the program manager for the MCP program which includes certifications. There continues to be quite a bit of discussion around certifications, so it only makes sense that we give our take on the matter. Both Steve and I are certified, so this may give away some of our thoughts.
Certification is a tricky thing. Much of the value you get out of a certification is dependent on where you on in your career and what your next step is going to be. This is going to be different for every person, so this decision is one that only you can make. This can make a decision on which certification to get and even when to get it a challenge.
Our conversation really revolves around what a certification will get you and what it won't help you with. Do you agree with our list? Let us know!
After a brief hiatus, we are back on the air to continue the conversation and let me tell you--we have a great conversation lined up for this episode. The discussion around what will happen to the relational database, and by extension us as administrators continues to get quite a bit of traction. Even within SQL Server, we are starting to see more features that don't fit the traditional relational mode and a podcast listener inquired about getting our thoughts. As I thought about a guest for this episode, I didn't want to get someone tied to a product. They, like me, would be biased and I wanted to get someone a bit removed from the situation.
Our guest today is Andrew Snodgrass, the research vice president at Directions and we chat about the future of the relational database and what the future of the data environment we manage might look like. I hope you will find his insights valuable as an outsider. While we don't get into the specifics of what databases are mostly like to be around, Andrew does give us administrator some idea's on what technologies we should start exploring.
What are your thoughts around the future of the relational database? Join the conversation and let us know!