Protecting authorship of sql code.

  • What are the recommended steps to insure the code that I create, is portable to me in authorship and copyright and mobility?

    For example, I work for a company that I write code for, however, I would want to take my code with me to another site, just as another trade would take their tools to a new shop.

    For Sql code, is there a way to wrap it up?

    Long ago, I just to drop this in the code: /* Copyright (c) 2014 My name */

    Any thoughts? Does this work to keep my code accessible to me for future reference and use?

    Just thinking out loud. Thank you for your time.

    "I like spaghetti because my house is made of brick."
    ~Paul Wuerzner on illogicality 2/14/86 - 11/6/11 😎

  • Are you self-employed perchance?

    In every job I've ever held - it was pretty much a given that anything I developed while working for them was a workproduct that the company owned. Unless it was highly generic, utility-type functions, three is VERY little I could have taken with me without strenuous legal repercussions. In the last three jobs - there was a specific document explicitly outlining things that had to be signed as a condition of employment.

    When I worked independently, I did have occasion to build out "reusable elements" that I brought in with me. That said they were spelled out in writing BEFORE I brought them into the code I was building for this company, and I negotiated to charge them for the *use* of the component. Anything I built for them however I could not take with me.

    I'd be kind of shocked if you could just start stamping copyright on stuff and get away with it. Even worse if you were to simply take the code with you when you leave (that's what the lawyers would call a "cease and desist order").

    ----------------------------------------------------------------------------------
    Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

  • If you are an employee you probably have something in your employment agreement that states that the company owns the code you write on their time and/or their equipment. That has been in every employment agreement I've signed. Usually independent contractors have the same thing in the contracts they sign with companies and, as Matt has already said, you need to have exclusions put in for generic code you bring with you. There is actually a fairly large placement firm in the US that I won't sign an agreement with because of the language about code ownership and I don't think anyone should because it basically says that the company you are placed with will own all code you write or use while on assignment there, which means you can't use Glenn Berry's performance scripts or Brent Ozar Unlimited's Blitz scripts.

Viewing 3 posts - 1 through 2 (of 2 total)

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