Voice of the DBA

Author: way0utwest

  • TTYL

    Please don’t communicate like this in business.

    Today’s editorial was originally released on Nov 20, 2007. It is being republished as Steve is at DevConnections.

    OMG! The DB if FUBAR.

    The sysop added an HDD and did a RAID rebuild OTF. AFAIK, the Vol with the MDFs got wiped for the CRM that runs 24/7.

    I’m ROFLMAO. AWHFY? TTYL.

    Can you imagine someone talking to you like that. I mean actually speaking with “words” like “T-T-Y-L?”

    I saw this article about how most people are speaking English in business today, but with the globalization of many companies, it’s easy to not only mis-communicate, but also offend. And that can be a big problem with not only co-workers, but also customers.

    Whether we standardize on English or some other communication, I hope that we continue to keep the skills of our language alive. The new generation of workers, working in shorthands and their own slang, seem to be losing out on the ability to effectively communicate with others. Too often they want to bang something out on a keyboard rather than talking directly to someone.

    I’m sure I sound like an old man, lamenting the good old days of paper, ink, and phones without voicemail. However it’s not the shorthand or slang that bothers me as much as the lack of the ability to clearly articulate themselves that plagues many people in the IT world. When I started in this business, it was always an issue communicating because things were so highly technical and few people understood how computers worked. The geeks that could truly make a computer sing had trouble communicating with business users.

    I think the same thing is true today with communication, despite the advances in making computer interations simpler, greater familiarity, and a comfort level with technology by many business users. For every step we’ve made in computing becoming more accepted by users in all aspects of society, we’ve gotten worse in our overall communication skills with acronym and shorthand overload. I almost shudder to think of the text-messaging generation entering the workforce.

    Technical jargon is important. It helps us quickly, clearly, and easily communicate with other IT workers with very specific meanings, but it’s not the way that we should communicate with those outside of IT. Even if you are never any type of analyst, designer, architect, it pays to be able to clearly and effectively communicate your ideas, thoughts, and concerns to others.

    Save the shorthand and slang for those times when it’s appropriate and be sure that you can communicate using clear and generally accepted English (or your native language) with everyone else you encounter in your career.

    Steve Jones

    The Voice of the DBA Podcasts

    Everyday Jones

    The podcast feeds are now available at sqlservercentral.podshow.comto get better bandwidth and maybe a little more exposure :). Comments are definitely appreciated and wanted, and you can get feeds from there.

    The RSS Feed: or now on iTunes!

    Today’s podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.

    I really appreciate and value feedback on the podcasts. Let us know what you like, don’t like, or even send in ideas for the show. If you’d like to comment, post something here. The boss will be sure to read it.

  • Question what you think

    Good advice from Jeff Bezos.

  • DBA Support

    There was a time when I managed two production databases on SQL Server. Two. I had a development version of one database where we paused development for testing, and only two production databases to manage. Since I had to also handle development, application support and hardware repair/replacement, that seemed like plenty to me. I was the accidental DBA, with database administration being the lowest priority of my day.

    After that I moved on to administer databases in a number of jobs, sometimes as a priority, sometimes not, but in each case, I learned to work more efficiently and effectively. My goal was to automate as much as possible of the routine work so that I could spend my days adding value to the company. I learned to use scripts, alerts, jobs, and more to keep systems running while I was doing other work.

    I’m sure many of you work in a similar manner, or at least I hope you do. This Friday I wanted to ask you at what scale do you need to become efficient, based on the size of your organization. The question this week is:

    How many databases does each DBA in your organization manage?

    I know some of you manage lots of databases in raw numbers, but also let us know if you need to do much with these databases. Is maintenance automated, or is there much active management you need to do in order to ensure these databases are running on a weekly basis. Let us know the size of your load as well, perhaps the amount of data is a better way of measuring the DBA load.

    Steve Jones

    The Voice of the DBA Podcasts

    We publish three versions of the podcast each day for you to enjoy.

  • Two Steps Ahead

     

    think ahead
    Are you thinking ahead? Using the data from your systems to be proactive?

    Exceptional DBAs do more than respond to events and issues in their environments. In many cases, I think they even go beyond using metrics that detect problematic activity on their systems before users notify them. I think the best DBAs will actually mine the information they have about their systems to anticipate problems in advance.

    In the past I’ve had monitoring systems that would respond to issues, and I had alerts setup on the system to notify of unusual events, like an unexpected data growth. What I had started to do before I became a manager was start to write system checks that anticipated future problems and allowed me as much lead time as possible to prepare for issues. An example of this was a set of queries I wrote that calculated data growth for all databases on an instance and then used that to calculate how many days would elapse before I ran out of space on the data drives.

    You can write similar queries to look for other trends. Tracking the execution times of often-run queries, or those queries which are important to the application can allow a DBA to find potential issues. If the execution times are growing, the DBA can anticipate a problem occurring in the near future and begin taking action to rewrite, tune, change indexing, or some other measure. A broad spectrum of queries taking longer might be an indication that hardware needs to be upgraded. There’s even a site devoted to metrics.

    Instrumentation is important in understanding, analyzing, and predicting system performance. More and more tools are being released to gather detailed metrics on .NET code, in browsers, and more, but there is a wealth of information inside SQL Server on the performance of the platform. A little work can help you track and monitor the performance of your system and proactively maintain performance before your users complain.

    Steve Jones

    The Voice of the DBA Podcasts

    We publish three versions of the podcast each day for you to enjoy.