I’ve grown up reading Tom Clancy and probably most of you have at least seen Red October, so this book caught my eye when browsing used books for a recent trip. It’s a fairly human look at what’s involved in sailing on a Trident missile submarine…
Have you ever heard the phrase “Hold The Fort”? Long ago in battle supply routes were targeted by enemy regiments that would cut off rations to fighting units. As the battle ensued the enemy had driven back their counterparts to a small area on a hill. They were being overwhelmed with many wounded and dying; that is until in the distance they noticed reinforcements were on the way.
How many times have you, as a data professional, been stuck wondering the same thing? Battered, worn down, and flat-out exhausted until you look and see reinforcements on the horizon. Sure, we’ve all been there, but to some it is a question of how do I call in re-enforcement’s or how do I even go about sending out a help signal? Below are some various ways you can tackle problems:
There are several forums out there that can provide some great insights into similar issues that you may be experiencing. To a certain extent I think forums are a great avenue to explore potential solutions. With that said however you cannot take every answer verbatim. There can be some off the wall answers out there that shouldn’t be followed. It is important to test anything you find on the web regardless of who it comes from.
You can find some of the forums I frequently attend here.
One thing that I’ve learned about the community is the willingness to help each other out. Remember above when I stated “Hold the fort, and reinforcements are on the way”; this is a good twitter hashtag to be familiar with. Professionals from all over the world take this seriously and it is not to be mistreated on how it is utilized. I have received great assistance in the past on issues I’ve been stuck with.
Phone a friend
We all have our “go to group” we bounce ideas off of. Sometimes it is helpful to bounce ideas off of another data professional. You may surprise yourself and actually start talking through your problem and come to an answer you may not have arrived to had you not initiated the conversation.
Old Fashion Testing
As a data professional you cannot be afraid to get your hands dirty. Prove your theories and test the scenarios as you run across them. One should be doing this anyway, but in doing so a wealth of knowledge gained is at your fingertips. We stop learning when we stop trying; just because you encounter one failure doesn’t mean you stop. You keep fighting and beating down that door until you make it through the other side. How bad do you want it?
Is It A Vendor Product?
I have the opportunity to work with a plethora of vendors. Maybe your issue revolves around a vendor product and you are not able to make any changes. Great, this happens all the time to data professionals. Some questions I’ll throw out there are:
- Have you opened a dialogue with the vendor about the issue?
- Have you documented the issue; not just call and say I have a problem?
- Have you tried to reproduce the error?
- It it already a known bug?
- Is it something that we can address internally before we talk with the vendor?
I’ve worked with a couple great vendors in Red Gate and SentryOne over the years. As a data professional I’ve seen vendors (not all) take pride in a quick response time. If there is an issue with a product they will want to take care of it in a swift manner or provide feedback as to why, when, and what to expect.
I’m going to say this here, and it may shock some of you. No one knows everything; there may be some who elude or perpetuate appearances that they know everything there is to know, but that is not the case. Whether you are in a shop or maybe a consultant (who can tap into their contact base) there are internal methods to maybe approach a different business unit or tech unit on an issue to get an outside perspective. Sometimes a fresh set of eyes goes a long way.
There are many great technical blogs out there; I have listed some in my DBA Blogs section to the right of this page. Each person is different and has their own go to Blog for review. I receive questions all the time from readers and other data professionals; being respectful is key but I have not seen one data professional out there who would not extend a helping hand if presented in a respectful manner. DO NOT TAKE this as one will provide an answer. We may show you how to connect the dots, but it is important one takes the necessary steps to get to the answer on their own. Nothing is given….work hard for it.
Maybe your issue is not a hot ticket item and it can wait to a user group meeting. These are great places to bring up questions and issues in a local environment with some pretty stellar professionals. I guarantee that if you ask a question and no one knows the answer then someone will do their best to find out that answer and further the discussion. An example of a user group can be found here.
Perhaps your issue is ongoing and you are at the PASS Summit. Great, besides being at a conference with over 6k of our closest friends I would take advantage of the SQLCat and AzureCat Team’s hours. It is a great way to tell Microsoft of your issues and get advice from some of the top-tier people in our industry.
I don’t know what your situation is or will be. Obstacles will come from all angles this year; it is up to us on how we deal with them. I would be amiss if I sat here and didn’t tell you that it won’t always be easy. Nothing in life is easy; some days you will have to work and grind your way through until you get to an answer for an issue. In the end though, when you do find that answer (and you will) you will be able to learn from it and move on. It is part of a data professionals journey.
Keep fighting and keep working toward your end goals. Never stop learning; never stop gaining knowledge.