Category: Editorial

  • I lied, now what?

    Not the best policy on the job.

    You have a job and realize that you’re in over your head. Perhaps you misled a manager that couldn’t really evaluate your technical skills, or maybe you memorized enough answers from Books Online to get through in interview. It could be that you took a test during the interview and used your cell phone to post the questions on SQLServerCentral and someone gave you the answers.

    Now you have been given a project and you don’t have the skills to complete it. You can’t ask for training or consulting help since you should know this stuff.  What do you do now? Should you continue to deceive your boss and ask for free help on the Internet? Can you muddle through it and hope that you don’t do anything that causes damage to the company?

    It’s a tough spot. I realize that you have bills, obligations, perhaps a family to take care of. Losing your job could impact other peoples’ lives. However my advice would be to be honest with your boss. Let him or her know that you need help, and move forward from this point.

    No matter what your skill level, you should be making an effort to grow your skills. You should be taking advantage of any help given to you by others to learn more.  If you are making an effort, learning to close the gap between your skills and your claims of knowledge, you should be fine. Your boss will be more understanding of you asking for help than he will be if your efforts fail and your deceit is uncovered.  Most people are willing to give others second chances, especially when they are working to make amends.

    If you’re just coasting, and happy to ask others to write your queries and not improving yourself, then good luck. At some point you will be exposed, and likely fired. And you would deserve it.

    Steve Jones

    (published at http://www.sqlservercentral.com/articles/Editorial/72367/)


    The Voice of the DBA Podcasts

  • Cloud Hacking

    Hackers are training for the cloud challenges

    Not everyone is down on the cloud. Apparently someone found a great use for pay-as-you-go computing in the cloud by using it to hack wireless networks. What’s next, someone using Amazon’s Mechanical Turk to find security holes in police patrols of local businesses? It constantly amazes me just how someone will take a technology that is very handy and turn it into a tool used for criminal purposes. I suppose we just have to live with this use of technology and learn to protect ourselves as much as possible.

    I think that security will be one of the bigger impediments to cloud adoption than anything else. Sure there’s the cost factor of data transfers, and trying to determine how to manage the costs of large bursts. There’s the need to integrate local and cloud development codebases, and potential patching/version issues. However those are not large issues when compared with the potential security issues that come with cloud computing.

    Even as we move to private cloud structures, we may have security issues with more resources being grouped under one large services umbrella and the difficulties of managing security for large numbers of users. We want to use groups to make management easier, but the more people you manage and the more groups that become involved, the more likely it is that you will have some security hole in your system.

    I think we’ll start to find more hackers that will discover, and take advantage of, hole in cloud security that we haven’t thought of. As they do, we’ll see more resistance from companies in migrating their infrastructures. At least until it becomes more cost effective to do so. Then we’ll discover that many of those security issues don’t seem to matter quite as much.

    Steve Jones

    (published at http://www.sqlservercentral.com/articles/Editorial/72385/)


    The Voice of the DBA Podcasts

  • Hybrid Hires

    I'd like to see more of these in the US

    There was a lot of talk about various hybrid technologies at the recent Detroit Auto Show, with many new models being displayed that use some type of hybrid technology. There are plenty of people that don’t love the technology, but my Prius has performed well for me over the last three and a half years I’ve had it. Who knows, I might even buy another one.

    The past two or three years have been a down economy around the world. As I’ve traveled to meet many SQL Server professionals at events all around the US, I’ve found that many of them have struggled with having more work and less resources to get it done. There are also many people who have lost their jobs or had trouble finding a job. Quite a few others have a hard time trying to get work done while worrying about their own job security. The downturn has not been pervasive, however, and there are plenty of technical professionals for whom the last two years have been business as usual as they go to work every day.

    At some point most of us will need to look for another job, and when we do, I think those of us that are well rounded DBAs will be in a good position. Data professionals often understand technology, and the business impact of data. There was some data on recent good trends in IT hiring summarized in this article that talks about job growth. In the article it mentions how there are lots of potential IT related positions where people are being hired to analyze data and statistics, as business/IT hybrids.

    I’m not sure that the idea of being a hybrid worker appeals to me, but I can see where technical and business skills are valuable for a data professional. You want to use these skills to market yourself and bring attention to your resume. It’s why a good IT worker will learn about the business of their employer and how it works.

    When you’re looking for a job, showing off your business skills alongside your technical skills can give you more opportunities to choose from and hopefully help you find the job that fits you best.

    Steve Jones

    (originally published at http://www.sqlservercentral.com/articles/Editorial/72344/)


    The Voice of the DBA Podcasts

  • What’s a Passive Server?

    Licensing software is often a more complicated process than I think it should be. Licensing database software seems to be even more difficult to understand, especially when you start to talk about the various high availability (HA) scenarios, virtualized  servers, separate machines to process SSIS packages and who knows what other configurations, not to mention the licensing changes with each new version of SQL Server.

    I was following a licensing debate  about how you license passive servers in an HA situation. I have always understood from the SQL Server licensing documents that if you have a passive server, it does not require a license for the SQL Server software. However it’s not that simple, or at least, it doesn’t appear that way to me.

    Suppose you have an primary instance that mirrors its database to another server. The mirror instance doesn’t need a license for that database, but what about if you also log ship your primary database to a third server? Does the third server need a license if it’s also “passive”? I assume that if you had second database on the mirror instance being used for another application, you’d need a license for that instance, but what if you only have a “DBA database” that gathers performance monitoring information for that mirror database? Is that “passive”?

    Suppose I have a 6 node cluster, and I have 4 active nodes and two passive ones, do I still have 2 other “passive” licenses for log shipped servers? Or can I log ship to 4 separate servers? That doesn’t even bring this clause into play:  “The passive server can take the duties of the active server for 30 days. Afterwards, it must be licensed accordingly” (from 2005 licensing). It almost feels like I am studying some type of Microsoft Internal Licensing Framework in preparation for some type of certification.

    To me, the simple way to handle this is to say that passive servers, those not doing any work for the business that owns them, don’t require a license. The exception would be for internal monitoring or maintenance on the passive server (backup restores, DBCC checks, DBA sysadmin monitoring). I doubt we’ll get something that simple, but that’s what I think would be fair.

    Steve Jones

    (originally published at http://www.sqlservercentral.com/articles/Editorial/72338/)


    The Voice of the DBA Podcasts