我在一个学区工作。每年我们都必须从学生管理系统中导出一份学生名单，并将其发送给处理我们在线考试的公司。
所以为了做这个输出，我们必须雇佣一个了解我们学生管理系统内部运作的人。他写了一个sql (Adaptive Sybase sql Anywhere)查询，将学生导出到我们需要的csv文件。这是在我开始为学区工作之前，所以有一段时间我以为这是一个真正的应用程序，直到轮到我自己做导出的时候。
每年他都会向我们收取500美元来更新这个查询以导出当年的学生。所以当我发现它只是一个查询(.bat文件和.sql文件)时，我的想法是“我可以自己更新”。我所要做的就是改变查询中的年份(例如。2009 - 2010)。
查询(。SQL文件)本身在顶部有这样的注释:
// This code was writtend by [the guy]
// and is the property of [his company]...Copyright 2005,2006,2008,2009
// This code MAY NOT BE USED without the expressed written consent of
// [his company].
(是的，上面确实写着“writtend”。)
所以现在我老板担心我们侵犯了版权。那家伙会发现是我自己更新了查询因为我们今年还没有要求他更新并采取法律行动。
回到刚才的问题:
他真的能获得这个问题的版权吗?
如果是的话，我们自己修改是不是侵犯了版权?
在我看来，单个查询不是程序代码。它更像是一个命令行命令。但我不知道这在法律上是怎么考虑的。
我是一名DBA，使用过许多带有罐装SQL代码的第三方应用程序，我从未见过SQL语句附加这样的东西。如果你可以直接访问数据库并从中查询数据，那就重写代码，不要再给那个人一秒钟的时间，因为这样一个500美元的单进程似乎是一种敲敲敲敲。
But without seeing the code there's no telling how involved it is. I've written some SQL statements that go into hundreds of lines to get data, and they can take DAYS or even WEEKS to write and debug. If this guy invested that kind of time into the process and you're paying $500 per run, it may be worth it ... but if it's just a strait forward Select statement that's no more then a dozen or so lines long, that is not worth $500 and can be written by you or someone else with a basic understanding of SQL. Even if it looks similar to his, honestly sometimes there's only so many ways to write something. "The dog is blue"... how many ways can you say it? Not many :)
是的，我也不是律师，但当涉及到这样的事情时，我的道德准则是指导我的。
定义一个新的视图使用原始查询作为基础，而不指定日期参数。
create or replace view MY_VIEW as
select STUDENT_NAME, STUDENT_NO, CLASS_YEAR
from STUDENT_TABLE
where STUDENT_CLASS = 10
写一个新的查询从视图中选择应用日期参数，例如。
set DATE_PARM = '2009';
select STUDENT_NAME, STUDENT_NO, CLASS_YEAR
from MY_VIEW
where CLASS_YEAR = %DATE_PARM
any content can be copywrited, including SQL procs, which methods may be considered a trade-secret. SQL procs can be a component of an entire application which most all are copywrited, unless the are released to the public as freeware, open source or with a GPL. If you feel uneasy about infringing on the SQL proc you mentioned, all you have to do is slightly modify the SQL proc by using an alternative statement or add a dummy part to it which has no effect on the desired result. In the chemical products industry, for example: a cleaning product made by ECOLAB, whose mixture of active and inactive chemical ingridients is patented, has been imitated by several other competitors who sell basically the same product for much less. The way the got around infringing on ECOLAB's patent is to modify the content of one or more chemical ingridients by 1%. So, using this as an analogy, you can do the same to the copywrited SQL proc.
