MSSQL Use cases for elasticsearch stack?

Hi Guys,

Can someone please elaborate what could be use cases for MS-SQL? OR Database in general? I mean what kind of dashboards can be created our SQL data?


Some use cases I can think of:

  • Search use case where relevancy matters. I don't want only to get data that matches but I want to give my users the most relevant results first. Think about it like "Google" for your MSSQL data.
  • BI Like use case. I want to give insights to my users. I can compute every night a dashboard in MSSQL by running a batch which is going to aggregate data or I can do that in real time any time I want without having to prepare any script or batch. I just ask for any insight when I actually need it.
  • Performance. I want that my users get results in some milliseconds, not seconds or minutes
  • Scale. Scaling can be hard and very costly for traditional RDBMS. Not a problem with elasticsearch.
  • Offload my MSSQL database. By running queries on elasticsearch instead of MSSQL you will use MSSQL for what it is very good at: storing and getting data by ID (and CRUD in general). Then instead of using lot of CPU for searching on your MSSQL DB you will use Elasticsearch instead. Elasticsearch is built for search.

My 2 cents

1 Like

I see I am mean since I am network security admin I am looking from that perspective. Like the top query executed, by whom, where is the database accessed, who accessed, modification time etc?

Something like what packetbeat, filebeat, metricbeat can give you?

Yeah especially filebeat? I mean not sure what could be the use cases for MS-SQL -

Like I need to start logging of SQL server into Windows Event
Then capture those events from winlogbeat?

To be specific I believe enabling Database and Server audit and let that log into System/Application events and then forward those to elsaticstack.

I moved your question to #beats where I believe you can get more information about what can be done regarding collecting MSSQL service related data.

With beats you can collect any kind of logs MS-SQL can write. If possible I'd prefer logging to files instead of Windows Event Logs. Collecting logs via Windows Event Logs can be much slower in comparison to files.

Regarding packetbeat we does not support TDS right now (See

Same for metricbeat. MSSQL would be a great addition to metricbeat. Feel free to open an enhancement request:

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.