简体   繁体   English

将Elasticsearch与SQL Server集成的影响

[英]Impact of integrating Elasticsearch with SQL Server

I want to use Elastic search for full text searching in mu SQL server. 我想使用弹性搜索在mu SQL Server中进行全文搜索。 As i read I can index my SQL server by elastic search. 当我阅读时,我可以通过弹性搜索为我的SQL Server编制索引。 My questions is about resource usage. 我的问题是关于资源的使用。 As I understood by indexing I must duplicate my entire SQL server database. 据索引了解,我必须复制我的整个SQL Server数据库。 and I must take both elastic and SQL server sync. 而且我必须同时进行弹性和SQL Server同步。 Am I wrong? 我错了吗? Thanks 谢谢

Yes, you are right. 是的,你是对的。 I also maintain a sql server + elastic environment. 我还维护一个sql server +弹性环境。

  • You need a separate instance of elasticsearch running. 您需要一个单独的elasticsearch运行实例。
  • You will have to index / insert all your existing data from sql server to elastic. 您将必须将来自SQL Server的所有现有数据编制索引/插入到Elastic中。 There are libraries for almost any language to easily insert data. 几乎所有语言都有库,可轻松插入数据。
  • You will have to sync these two in order to keep the data up to date. 您必须将这两个同步,以使数据保持最新。
  • In theory you only need 1 instance / node of elastic running, but it is recommended to have a full cluster, due to failover, etc. 从理论上讲,您只需要1个实例/节点即可运行弹性,但是由于故障转移等原因,建议您拥有完整的集群。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM