Exploring Facts About SQL Server Tables: Stairway to Exploring Database Metadata Level 5

  • Phil Factor

    SSCoach

    Points: 19903

    Comments posted to this topic are about the item Exploring Facts About SQL Server Tables: Stairway to Exploring Database Metadata Level 5

    Best wishes,
    Phil Factor
    Simple Talk

  • h.tobisch

    SSCommitted

    Points: 1671

    just for convenience,

    coalesce(object_schema_name(Referencing_ID)+'.','')+ --likely schema name

    object_name(Referencing_ID)+ --definite entity name

    coalesce('.'+col_name(referencing_ID,referencing_minor_id),'') AS [referencing],

    may be written as

    concat(object_schema_name(Referencing_ID)+'.', --likely schema name

    object_name(Referencing_ID), --definite entity name

    '.'+col_name(referencing_ID,referencing_minor_id) ) AS [referencing],

  • akljfhnlaflkj

    SSC Guru

    Points: 76202

    Wow, what a great article. This is going to take me a while to really go over in depth.

  • Phil Factor

    SSCoach

    Points: 19903

    Thanks. @IwasBornready

    This series has been received quite quietly so far, so it is nice to know that someone appreciates them!

    Best wishes,
    Phil Factor
    Simple Talk

  • Robert Sterbal

    SSChampion

    Points: 10967

    Which of the scripts do you think I need permission to reproduce on my company wiki?

    Do I have your permission? Was this written in the course of you employment or as an independent contributor?

    412-977-3526 call/text

  • Phil Factor

    SSCoach

    Points: 19903

    @Robert,

    This is fine on a company Wiki that is accessible only to your company, with an attribution to the source. Redgate, who own this site, are only concerned with protecting authors' intellectual property on this site against any unauthorised publishing: 'Publishing' means making the authors' property publicly available in a website, book, presentation or whatever without consent of the author. A private group such as your company is fine as long as you mention where it came from. I need the clicks!

    SSC have permission to be sole publishers of this article, which remains my Intellectual property. This arrangement allows SSC to prevent rogue sites from copying our content.

    A lot of people collect scripts from SSC to use at work, and make available to others within the workplace. That's what SSC is for.

    I hope that answers the question!

    Best wishes,
    Phil Factor
    Simple Talk

  • Robert Sterbal

    SSChampion

    Points: 10967

    Unfortunately the policy requires that I ask permission for each copyrighted script or article that I want to copy.

    I'd be grateful if you took a look at my forum item about the terms of use:

    http://www.sqlservercentral.com/Forums/Topic1838731-433-1.aspx

    On another topic:

    How do you feel about this link?:

    https://sqlserver.miraheze.org/wiki/RedGate%27s_Free_eBooks

    412-977-3526 call/text

  • Phil Factor

    SSCoach

    Points: 19903

    @robert

    I expect that RedGate would be happy about the link because they are linking to the Redgate site. Where might be the problem?

    Re: copyright: I'm no lawyer, but I reckon that the SSC site is fine about you using SSC content for private use, including the workplace. I would positively like you to use it. After all, code, and sharing code, is what the site is about. In some cases, there is only one correct way of coding a particular routine, and it is almost impossible to determine who thought of the idea of doing things a certain way. Anyway, I suspect that your company would be relaxed if you only have to ask each author once. You are welcome to use any of my code for private or workplace use. I guess all authors would be the same but I can't speak for them. The problem with any site like this is that it relies on loads of contributions and so the publishers, Redgate, own publication rights, but not the IP. How do you suggest it should work? I know that Redgate only take ownership of publication rights so they can act on the authors behalf to prevent plagiarism. Surely, they can't give anyone the blanket rights to copy content that doesn't belong to them? Nobody is concerned with everyday use of code, but would worry about re-publishing or plagiarism.

    Best wishes,
    Phil Factor
    Simple Talk

  • Robert Sterbal

    SSChampion

    Points: 10967

    My main hope is that people actively address the copyright of their scripts separately from their articles.

    Give them a list of options when they publish a script:

    1) Not under copyright

    2) creative commons and its variants

    3) copyrighted

    It would be helpful if a license line for the content read something like this:

    Material licensed from copyright holder: X

    412-977-3526 call/text

Viewing 9 posts - 1 through 9 (of 9 total)

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