Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQLServerCentral content restrictions


SQLServerCentral content restrictions

Author
Message
lnoland
lnoland
SSC-Enthusiastic
SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)

Group: General Forum Members
Points: 140 Visits: 785
Were you guys aware that SQLServerCentral doesn't allow any of the content you guys post here to be used for any commercial use? I was looking over the terms of use and was kind of shocked to see the following:

4.2 [highlight=#ffff11]Any material contained in the Site (the "Red Gate Materials")[/highlight] and all intellectual property rights in the Red Gate Materials are either owned by us or have been licensed to us by the rights owner(s) so that we can use those Red Gate Materials as part of the Site. You are only allowed to use the Site, the Red Gate Materials and any intellectual property rights in them on the basis of these Term of Use.

4.3 [highlight=#ffff11]You are not permitted to copy or use any of the Red Gate Materials for any purpose[/highlight], although you may print a copy of any page of the Site for your [highlight=#ffff11]personal, non-commercial use[/highlight]. Replication of content through feeds is not permitted. Feeds are limited to 500 characters and must include a link to the relevant content on sqlservercentral.com.


That seems like a pretty harsh restriction for a site like this. I've learned a lot here and luckily they can't take away what I've learned but as for all the great code examples, etc., that you guys have shared, if I want to take advantage of them, apparently my only choice is to reinvent the wheel. I have been a great fan of this site but this leaves a bad taste in my mouth.

- Les
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47145 Visits: 44346
I suspect that's there to 'prevent' someone from copying the entire scripts collection, sticking it on a DVD and selling it, or collecting the articles into an ebook and selling it on amazon, not to stop you from using something posted here in your job.


Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


lnoland
lnoland
SSC-Enthusiastic
SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)

Group: General Forum Members
Points: 140 Visits: 785
It's possible that you are correct about the intent but the effect of the wording is the same, nonetheless. I can't really subject my company to liability over the use of some code which wasn't authorized, however unlikely it is to actually become an issue, so even if I find something on the site which is exactly what I need to solve a problem -- Steven Willis's excellent virtual tally table comes to mind -- I pretty much have to find some way to implement something on my own which uses the same principles but avoids using the actual code -- which seems pointless and tedious and I suspect was probably not what Mr. Willis or most of the other contributors had in mind when they so generously shared their code.

There are plenty of other websites around which openly allow use of code shared on the site - their owners obviously didn't feel the need for such restrictions. I'm not a lawyer but I suspect that there are ways of restricting the use of entire collections of information without needing to restrict isolated instances.

- Les
Grant Fritchey
Grant Fritchey
SSCoach
SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)

Group: General Forum Members
Points: 17529 Visits: 32252
I've checked in with the powers that be. I suspect pretty strongly that you're misinterpreting that statement, but someone should get back on this, soon I hope.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
venoym
venoym
Ten Centuries
Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)

Group: General Forum Members
Points: 1353 Visits: 2082
I would think that the below is simply to say "You can't reproduce it in an article or sell it as it is." If you read 4.2 closely the prohibition appears to be on Red Gate materials not on all materials on the site. However it can be easily read that they have licensed the materials and can exert influence to remove blatant plagiarism or theft. Using the content of the forum in your company for commercial purposes does not appear to be prohibited as long as it is code in a working product and not a book or article using wholesale from the site.


lnoland (5/28/2014)
Were you guys aware that SQLServerCentral doesn't allow any of the content you guys post here to be used for any commercial use? I was looking over the terms of use and was kind of shocked to see the following:

4.2 [highlight=#ffff11]Any material contained in the Site (the "Red Gate Materials")[/highlight] and all intellectual property rights in the Red Gate Materials are either owned by us or have been licensed to us by the rights owner(s) so that we can use those Red Gate Materials as part of the Site. You are only allowed to use the Site, the Red Gate Materials and any intellectual property rights in them on the basis of these Term of Use.

4.3 [highlight=#ffff11]You are not permitted to copy or use any of the Red Gate Materials for any purpose[/highlight], although you may print a copy of any page of the Site for your [highlight=#ffff11]personal, non-commercial use[/highlight]. Replication of content through feeds is not permitted. Feeds are limited to 500 characters and must include a link to the relevant content on sqlservercentral.com.


That seems like a pretty harsh restriction for a site like this. I've learned a lot here and luckily they can't take away what I've learned but as for all the great code examples, etc., that you guys have shared, if I want to take advantage of them, apparently my only choice is to reinvent the wheel. I have been a great fan of this site but this leaves a bad taste in my mouth.

- Les

Andrew Clarke-161005
Andrew Clarke-161005
SSC Rookie
SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)SSC Rookie (31 reputation)

Group: Administrators
Points: 31 Visits: 52
Yes, you're right, it is definitely a mistake. As Gail has pointed out, it was done at a time when the site was suffering from the community's contributions being plagiarized by several sites. The wording was intended to allow us to take legal action against out-and-out plagiarists easily on behalf of the community, and the last thing on our minds was any desire to stop legitimate use of what the community has submitted. We're getting it changed as soon as we can find an acceptable wording. I would have written ‘You are not permitted to republish any of the Red Gate Materials for any purpose without explicit consent from the owners of the intellectual property’, but then I'm not a lawyer!

In the meantime, if anyone needs an assurance about using any of the materials on the site for their work, then drop Steve, Tony or I an email.

Editor: Simple-Talk
lnoland
lnoland
SSC-Enthusiastic
SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)SSC-Enthusiastic (140 reputation)

Group: General Forum Members
Points: 140 Visits: 785
Andrew Clarke-161005 (5/30/2014)
Yes, you're right, it is definitely a mistake. As Gail has pointed out, it was done at a time when the site was suffering from the community's contributions being plagiarized by several sites. The wording was intended to allow us to take legal action against out-and-out plagiarists easily on behalf of the community, and the last thing on our minds was any desire to stop legitimate use of what the community has submitted. We're getting it changed as soon as we can find an acceptable wording. I would have written ‘You are not permitted to republish any of the Red Gate Materials for any purpose without explicit consent from the owners of the intellectual property’, but then I'm not a lawyer!

In the meantime, if anyone needs an assurance about using any of the materials on the site for their work, then drop Steve, Tony or I an email.


I really appreciate the response and definitely think that they need to change the wording. Like I said, I really like this site and have learned a tremendous amount by coming here and would hate to see it hampered by a restrictive policy which seems at odds with the purpose of the site. While the code snippets in many cases are simply good examples of usage or demonstration of a principle and therefore don't really need to be used verbatim, there is the occasional inclusion of a fully realized tool that is very useful. While I doubted that there was ever a significant risk from using something I found here, I don't have a right to subject my company to any such risk. And while I would likely still come here regardless, there are others who might read the terms of use and just move on since there are other sites which don't have such restrictions. That would be unfortunate for both us and them.
OCTom
OCTom
SSCrazy
SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)

Group: General Forum Members
Points: 2813 Visits: 4152
Even if the wording is not changed, I can't see how anyone would use any code samples without making it their own. If I copy a bit of code, I will need to change server names, table names, etc. I may not like the varaible names the author has, so, I will change those. What remains is the concept and no one can take that away.

Changing the aggreement to clear things up is a good idea, though.

Tom
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search