Author: way0utwest

  • The New DBA

    What does DBA mean? It’s traditionally meant Database Administrator for technologists. However it’s also been a synonym for a database developer, or even anyone that has raised privileges on a database system. The term has been expanded to people designing databases, and usually includes the BI developers or analysts that work with database related technologies.

    In short, it’s been a vague term that means different things to different people. However as I look forward, I think there’s another interpretation I have. The people functioning as DBAs, are the Data Bridges to Applications. We take the data and find ways to ensure it’s useful to applications. We make sure it’s available. We connect systems together. We do the dirty work of cleaning data. We secure the bridge.

    We really are the person that needs to answer any question about the database. Throughout my career, when a company has decided to use DBAs, I have found the DBA is usually the catch-all person that really needs to be able to do whatever is asked of them that might tangentially relate to a database.

    While there have always been DBAs that tightly controlled their systems and acted as impediments to change, I think those positions are disappearing fast. More and more companies, if they even bother to hire DBAs, want those individuals to ensure data is useful. Whether that’s administering, developing, configuring, or anything else related to data, whether the data is in an RDBMS, Access, Excel, the cloud, NoSQL, any anywhere else, we need to be able to provide some solution to gets data to an application.

    Steve Jones

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 2.1MB) podcast or subscribe to the feed at iTunes and LibSyn.

  • Congrats Summit 2015 Speakers

    I'm Speaking Graphic_SmallThe PASS Summit 2015 Speaker list has been released and I wanted to congratulate everyone that was accepted. It’s a great honor and I’m proud to be on the list once again.

    I also apologize to everyone that submitted and wasn’t accepted. I hadn’t planned on submitted, but part of my job is speaking to the community. I was asked to submit sessions, which I did. Of the three I submitted, one was accepted.

    I saw a post from Mark Broadbent (@retracement) today that talks about his submission experience this year. He’s spoken at the Summit before the Rally, and numerous SQL Saturdays. He’s got experience and success as a speaker. It’s hard to call a single session selection a failure, and I hope Mark doesn’t feel that way.

    It’s Not You

    One of the things I’d like to say is that if you submitted a session and weren’t picked, it’s not necessarily you. This is certainly true for the Summit, but the same thing can apply at SQL Saturdays or other events.

    I’m sure you doubt I know what I’m talking about, and that might be true, but I certainly understand how you feel. I’ve received two rejections this year from events that didn’t like my submissions. It’s tough, and it can be a blow to your self-confidence, but it’s not necessarily you.

    Don’t get me wrong. It could be. Please solicit feedback from the organizers and friends about your submissions. There might be things that you are doing poorly, and if so, you should learn to do a better job at writing abstracts, and a better job of speaking. I regularly ask people what they thought of my talks, and I’m happy to go watch and give feedback to others as well.

    I’m sure some of you have heard of, or seen spoofs, of medical school grading where professors start a test letting students know that there will be x As, y Bs, z Cs, i Ds, and j Fs. In other words, a forced ranking where you must compete in order to succeed. That’s the PASS Summit submissions, but in a more complex scenario.

    You might submit a great abstract, on an outstanding topic. Maybe you’re a SQL Server memory guru and you want to put in a 400 level internals talk on memory pressure. Great. But if Adam Machanic submits on a similar topic, I bet you don’t get picked.

    In the various areas, sessions are ranked, and no matter how good a job you do, it’s possible you’ll get beat out by someone else. That’s not to say it’s hopeless. I believe that some slots are reserved for first time speakers (to the Summit, not in general), but it does mean that your abstract needs to be good AND not have great competition in your topic area.

    Submitting to the Summit and getting picked is a bit of a lottery. It helps to speak at multiple other events (user groups, SQL Saturdays, etc), and get some reputation, but it’s also important to pick topics that will be both interesting and don’t have lots of competition. It also becomes important to write a great abstract, and if you need help, read Adam Machanic’s post on this topic.

    Above all, don’t get discouraged. Get help in putting your submission together. Ask friends, ask colleagues, ask your family and read what others have done. Pick a topic area you’re comfortable with and try to find a niche that minimizes competition. Above all, make sure you get feedback from PASS and try to use that to tailor the next submission.

    You can do it. We see more and more new speakers every year, and you have a better chance if you think about how to best present yourself to the world.

  • The First SQL Saturday in South Dakota

    There have been so many SQL Saturday events in many places, and in most of the US states, but there are a few that have never had an event. One more state gets its first event this July, with SQL Saturday #427 in Sioux Falls, South Dakota.

    I’m proud to be speaking at the event, and I just finished booking my travel. I’ve never been to South Dakota, so I’m looking forward to wandering around a bit on Friday before we kick off the first SD SQL Saturday on July 18, 2015.

    I’m going to be talking about Continuous Integration in the afternoon, but there are some other great sessions. Learn about baselines, Service Broker, Auditing, SSAS, Stress testing, Reporting, and more.

    If you’re anywhere nearby, make some plans now to get to Sioux Falls in July for some SQL Server education.

  • #SQLNewBlogger

    In April, Ed Leighton-Dick set up a challenge to motivate new bloggers to begin writing about their knowledge of SQL Server. This is a passion of mine, and I believe this is one of the ways you can truly help interest potential employers in your work. It’s allows them to perform some due diligence, and I’ve had success in my career with employers being impressed with the knowledge I’ve shared through blogging.

    Ed made note of a new Twitter hashtag, #SQLNewBlogger, and there were a few people that participated in the challenge. However, there weren’t enough. I was really hoping to see more people join in, start blogging, and showcasing their knowledge. Therefore, I’m making an appeal here.

    Let’s extend the SQLNewBlogger. I’d like to change the rules a bit and see if I can motivate a few of you to start building your communication skills and showcasing your knowledge across the next year. Just like a class at a gym can motivate you to try harder and longer than you might otherwise, I’m hoping the #SQLNewBlogger tag can do that.

    If you’re thinking of asking for a raise, or looking for a new job next year, in 2016, do these things now:

    1. Set yourself a weekly reminder, and appointment, at a time when you can spare 15-30 minutes. Use this time to work on communicating, through writing.
    2. Get yourself a note taking system. You can use OneNote, Evernote, Remember the Milk, or Notepad. As you write queries, set up a system, or solve a problem, make a note of what you did. Pull out that list each week when the reminder you set in #1. Completely ignore anything anyone else has written on your subject and write your own thoughts.
    3. Make it a goal to get a 1-2 page post done each month. I’d like to think that in 1-2 weeks you can get one done, but find your pace.
    4. Use the #SQLNewBlogger tag to ask for help reviewing your post (you want good quality) and then finish one post a month. If you’d rather do this privately, have a friend review your work.
    5. You can get a free blog at WordPress, TypePad, Blogger, etc. You can choose to write and safe drafts forever, or publish posts for potential recruiters and employers to learn about your skills.
    6. Let us know what you wrote about. Either a link if you’ve published it for us to see, or a title if you keep the content private.

    That’s it. If it sounds like a lot, I’d remind you this is asking for 1-2 hours a month. 12-24 a week, to showcase your knowledge, grow your career, and maybe most importantly, improve your ability to write a sentence. We communicate constantly in this business, despite all the code we write, so learn to do it better.

    Next year, whether you publish publicly or not, you’ll have 12 things that show you have some knowledge about SQL Server. I’ve got a few references on setting up a blogchoosing topics, and writing better.

    I’d also like my fellow bloggers to encourage and cheer on the people making an effort to share some knowledge and grow their careers.

    Steve Jones

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 4.6MB) podcast or subscribe to the feed at iTunes and LibSyn.