通过 T-SQL 查询远程 MSIDXS
我认为这个问题比 ServerFault 更适合这里，但如果我错了，请纠正我。
我有一个系统，其中的数据库也查询 Windows 索引服务。查询是使用 OpenQuery(Linked_Server_Name, ...) 函数通过 T-SQL 完成的。 当数据库和索引服务位于同一服务器上时，一切都可以完美运行。
现在我需要扩展我的系统，这意味着我必须将数据库服务器与索引服务服务器分开。问题是，我找不到远程查询索引服务的方法。
有人通过类似的设置成功了吗？ 如果没有，您会建议什么替代方案？
I think this question better fits here rather than ServerFault, but if I'm wrong, please correct me.
I have a system which has a database that also queries Windows Indexing Services. The queries are done via T-SQL using the OpenQuery(Linked_Server_Name, ...) function.
When the DB and the Indexing Services are on the same server, everything works perfectly.
Now I need to scale my system up, which means I'll have to separate the DB server from the Indexing Services server. The problem is, I couldn't find a way to remotely query the Indexing Services.
Did anyone succeed with a similar setup?
If no, what alternatives would you suggest?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我在我的公司也遇到了类似的问题，我用谷歌搜索，远程索引是不可能的。但我们找到了解决方案。现在我们有一台带有数据库的服务器和另一台带有 IIS 和索引附件的服务器。解决方案是共享数据库服务器可以看到的附件文件夹（或者可能是整个光盘）。不幸的是，我在公司换了职位，我不再有权限连接到服务器来检查配置，所以我无法写下必须做什么以及在哪里完成。
I had a similar problem in my company and I googled, that remote indexing is impossible. But we found a solution. Now we have one server with DB and another server with IIS and attachments which are indexed. The solution was to share attachments folder (or maybe whole disc) that DB server could see them. Unfortunatly, I changed position in the company and I don't have permissions anymore to connect to servers to check for configuration, so I can't write what and where exactly must be done.
远程查询 MSIDXS 似乎确实是不可能的。我最终编写了一个包装 MSIDXS 并被远程调用的 Web 服务。
不过性能没那么好。
It really does seem impossible to remote query MSIDXS. I ended up writing a web service that wraps the MSIDXS and is called remotely.
Performance aren't as good, though.