SQL Server Analysis Services 中的自联接
我有一个这样的表：
WordId Set1 Set2 相关-wordId --------- ---- ----- -------- 101 A C1 105 102 B C2 101 103 A C1 102
然后我需要获取Word的Set1和Related-word的Set2之间的关联规则。
我使用了自引用并定义了 case/nested 表，但在依赖图的结果中，单词的 Set1 或 Set2 与父单词的 Set1 或 Set2 之间没有区别！
SQL Server Analysis Services 项目中的文本挖掘问题的最佳解决方案是什么？
I have a table like this:
WordId Set1 Set2 Related-wordId --------- ---- ----- -------- 101 A C1 105 102 B C2 101 103 A C1 102
Then I need to getting the association rules between Word's Set1 and Related-word's Set2.
I've used self-referencing and define case/nested tables but at the result of dependency graph there is no difference between word's Set1 or Set2 and parent-word's Set1 or Set2!
What is the best solution for this Text-mining problem in SQL Server Analysis Services project?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在 Analysis Services 模板中，我们可以使用自联接查询来执行此操作。
要打开模板，请右键单击模板名称并选择“打开”，或者将模板拖到已打开的查询窗口中。查询窗口打开后，您可以使用工具栏或查询菜单上的命令来帮助您构建语句：
要检查查询的语法，请单击“解析”。
要运行查询，请单击“执行”。
要停止正在运行的查询，请单击取消执行查询。
在屏幕底部的“结果”选项卡中查看查询结果。
切换到“消息”选项卡可查看返回的记录数、错误、查询语句以及与查询执行相关的任何其他消息。例如，如果您对在直接查询模式下运行的模型执行 DAX 语句，您可以看到由 xVelocity 内存分析引擎 (VertiPaq) 生成的 Transact-SQL 语句。
In Analysis Services Templates We can use self Join query to do this
To open a template, right-click the template name and select Open, or drag the template into a query window that you already opened. After the query window is open, you can use commands on the toolbar or Query menu to help you build statements:
To check the syntax of a query, click Parse.
To run a query, click Execute.
To stop a query that is running, click Cancel Executing Query.
View the results of a query in the Results tab at the bottom of the screen.
Switch to the Messages tab to see the number of records returned, errors, query statements, and any other messages that are associated with the execution of the query. For example, if you execute a DAX statement against a model running in Direct Query mode, you can see the Transact-SQL statement that is generated by the xVelocity in-memory analytics engine (VertiPaq).