The Robot DBA

  • I used to work for a company supporting other peoples software. I remember one of my colleagues looking at the original implementation of .NET and viciously asserting that "this will kill off all those cowboy developers".

    Similarly I can remember a comment on this site about clustering SQL Server. In SQL6.5 to SQL2000 it went from a "hey wow" skill to "So what"!

    Read Daniel Pink's Drive. He talks about human motivation and why carrot and stick is only really useful for dull mundane jobs that should be automated. People are self-motivated and enthusiastic when their creative energy is engaged.

    Most DBAs I know spend a considerable amount of time figuring out how to automate stuff so they can concentrate on the interesting stuff.

    SQL Server makes a wide range of DB tasks very simple. The problem comes in that people assume that something that is simple in SQL Server means that other niche products are simply bigger, faster versions of SQL Server requiring no particular skill.

  • Man I wish someone will automate my Jobs. Seems to me, I have enough work to last several lifetimes.

  • SQLRNNR (9/7/2011)


    jcrawf02 (9/7/2011)


    Ideally, using automation to replace workers would just require different and/or higher-level skills. The need for people to do *something* will never go away, the skills required will just change.

    Agreed. Skillsets will change and there should be that type of change. Making better applications that can work faster and more accurate is good. In order to make those apps and to continue to support them, we need to continue to evolve our skillset too.

    Yes, you both nailed it. This is actually an old economic topic. A specific task or even a job may be automated away, but that leaves an opportunity to invest in new innovation and efficency improvements by you or others.

Viewing 3 posts - 16 through 17 (of 17 total)

You must be logged in to reply to this topic. Login to reply