使用Microsoft Query和ODBC to SQL Server,复杂的查询
我在 SQL Server 中有一个与以下示例有些相似的视图。
SELECT *
FROM PEOPLE
LEFT OUTER JOIN (SELECT ID
FROM OTHER_TABLE
WHERE SOME_FIELD = 'x'
OR SOME_FIELD = 'y'
OR SOME_FIELD = 'z') AS PEOPLE_TO_EXCLUDE ON PEOPLE.ID = PEOPLE_TO_EXCLUDE.ID
WHERE PEOPLE_TO_EXCLUDE.ID IS null
麻烦:
我完全有能力无数次添加和修改“OR SOME_FIELD = 'w'”。不过,我正在为用户创建此视图,以便通过 ODBC 在 excel 中提取。用户需要能够根据自己的喜好修改内部选择,以匹配她在一天/周/月/年/等的某个时间碰巧限制的任何内容。我需要以一种允许她轻松限制 SOME_FIELD 的方式进行此操作。
有人对如何实现这一目标有建议吗?理想情况下,我可以给她一个视图,她可以在其中放置一个逗号分隔的值列表,而 SOME_FIELD 不能是。由于人们可能在 OTHER_TABLE 中有多行,所以我不能专门限制她对该表的限制。例如,某人可能有 SOME_FIELD = 'x',但表中也有一行 SOME_FIELD = 's'。此人应被排除在外,因为他们有“x”,尽管他们也有“s”。这就是为什么内部选择是必要的。
感谢您的帮助。
I have a view in SQL Server that is somewhat similar to the following example.
SELECT *
FROM PEOPLE
LEFT OUTER JOIN (SELECT ID
FROM OTHER_TABLE
WHERE SOME_FIELD = 'x'
OR SOME_FIELD = 'y'
OR SOME_FIELD = 'z') AS PEOPLE_TO_EXCLUDE ON PEOPLE.ID = PEOPLE_TO_EXCLUDE.ID
WHERE PEOPLE_TO_EXCLUDE.ID IS null
The hassle:
I am perfectly capable of adding and modifying "OR SOME_FIELD = 'w'" countless numbers of times. However, I am making this view for a user to pull up in excel via ODBC. The user needs to be able to modify the inner select to her liking, to match whatever she happens to be limiting on at that time of the day/week/month/year/etc. I need to make this in a way that allows her to easily limit on SOME_FIELD.
Does anyone have suggestions on how to accomplish this? Ideally I could give her a view, which she could put a comma separated list of values that SOME_FIELD cannot be. Since people may have multiple rows in OTHER_TABLE I can't just have her limit off of that table specifically. For example someone may have SOME_FIELD = 'x' but also have a row in the table where SOME_FIELD = 's'. This person should be excluded because they have 'x' even though they also have 's'. So that is why the inner select is necessary.
Thanks for your help.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
不要为 EXCEL 用户创建查询,他们总是会破坏它们,然后您必须调试它们。相反,创建一个存储过程,传入 CSV。在存储过程中,使用 split 函数拆分 CSV 并加入其中。用户只会有一个 EXCEL 查询,例如:
因此,他们不会破坏查询。
要帮助使用 split 函数,请参阅:"SQL Server 2008 中使用表的数组和列表-值参数”作者:Erland Sommarskog ,那么在 SQL Server 中分割字符串的方法有很多种。本文涵盖了几乎每种方法的优点和缺点:
您需要创建一个 split 函数。这是分割函数的使用方式:
我更喜欢数字表方法在 TSQL 中分割字符串,但在 SQL Server 中分割字符串的方法有很多种,请参阅前面的链接,其中解释了每种方法的优点和缺点。
要使 Numbers Table 方法发挥作用,您需要执行此一次时间表设置,这将创建一个包含 1 到 10,000 行的
Numbers
表:设置 Numbers 表后,创建此拆分功能:
您现在可以轻松地将 CSV 字符串拆分到表中并加入它:
Don't create queries for EXCEL users, they always break them and then you have to debug them. Instead, create a stored procedure, pass in a CSV. In the stored procedure split the CSV using a split function and join to it. The user will only have an EXCEL query like:
As a result, they will not break the query.
To help with the split function, see: "Arrays and Lists in SQL Server 2008 Using Table-Valued Parameters" by Erland Sommarskog , then there are many ways to split string in SQL Server. This article covers the PROs and CONs of just about every method:
You need to create a split function. This is how a split function can be used:
I prefer the number table approach to split a string in TSQL but there are numerous ways to split strings in SQL Server, see the previous link, which explains the PROs and CONs of each.
For the Numbers Table method to work, you need to do this one time table setup, which will create a table
Numbers
that contains rows from 1 to 10,000:Once the Numbers table is set up, create this split function:
You can now easily split a CSV string into a table and join on it: