History

Thales Macedo Garitezi 10425eb925 feat(resource): deprecate `auto_restart_interval` in favor of `health_check_interval` See: https://emqx.atlassian.net/wiki/spaces/P/pages/612368639/open+e5.1+remove+auto+restart+interval+from+buffer+worker+resource+options Current problem: In 5.0.x, we have two timer options that control the state changing of buffer worker resources: auto_restart_interval and health_check_interval. - auto_restart_interval controls how often the resource attempts to transition from disconnected to connected. - health_check_interval controls how often the resource is checked and potentially moved from connected to disconnected or connecting. The existence of two independent timers for very similar purposes is confusing to users, QA and even developers. Also, an intimately related configuration is request_timeout, which can interact badly with auto_restart_interval if the latter is poorly configured: requests may always expire if request_timeout < auto_restart_interval and if the resource enters the disconnected state. For health_check_interval, we attempt to derive a sane default that gives requests a chance to retry (if request timeout is finite, then the resource retries requests with a period of min(health_check_interval, request_timeout / 3). Another problem with the separate auto_restart_interval is that its default value (60 s) is too high when compared to the default request timeout and health check, leading to the problems described above if not tuned. Proposed solution: We propose to drop auto_restart_interval in favor of health_check_interval, which will be used for both disconnected -> connected and connected -> {disconnected, connecting} transition checks. With that, the resource will attempt to reconnect at the same interval as the health check, which currently is 15 s. Also, as two smaller changes to accompany this one: - Increase the default request_timeout from 15 s to 45 s. - Rename request_timeout to request_ttl.		2023-06-01 11:20:06 -03:00
..
include	refactor(sqlserver): move sqlserver bridge into its own app	2023-05-06 10:22:05 +08:00
src	feat(resource): deprecate `auto_restart_interval` in favor of `health_check_interval`	2023-06-01 11:20:06 -03:00
test	refactor(sqlserver): move sqlserver bridge into its own app	2023-05-06 10:22:05 +08:00
BSL.txt	refactor(sqlserver): move sqlserver bridge into its own app	2023-05-06 10:22:05 +08:00
docker-ct	refactor(sqlserver): move sqlserver bridge into its own app	2023-05-06 10:22:05 +08:00
README.md	docs: fix invalid links	2023-05-15 11:18:09 +08:00
rebar.config	refactor(sqlserver): move sqlserver bridge into its own app	2023-05-06 10:22:05 +08:00

README.md

EMQX SQL Server Bridge

Microsoft SQL Server is a relational database management system (RDBMS) that is developed and owned by Microsoft. Microsoft SQL Server offers a wide range of features, including support for high availability and disaster recovery, integration with other Microsoft products and services, and advanced security and encryption options. It also provides tools for data warehousing, business intelligence, and analytics, making it a versatile and powerful database platform.

The application is used to connect EMQX and Microsoft SQL Server. User can create a rule and easily ingest IoT data into Microsoft SQL Server by leveraging EMQX Rules.

Documentation links

For more information about Microsoft SQL Server, please see the official site

Configurations

Please see Ingest Data into SQL Server for more detailed information.

HTTP APIs

Several APIs are provided for bridge management, which includes create bridge, update bridge, get bridge, stop or restart bridge and list bridges etc.

Refer to API Docs - Bridges for more detailed information.

Contributing

Please see our contributing.md.

License

EMQ Business Source License 1.1, refer to LICENSE.