My Splunk DB Connect seems to have some data lost issue connecting to a MSSQL server where the DB is used as customer service loggings.
Has anyone face the same problem while tailing a datetime column and missing a few rows comparing data in Splunk and database?
This is why Splunk cautions against using timestamp/datetime as a rising column. Once DB Connect reads a set of rows, it asks for a new set consisting of rows with datetime column values greater than the value last read. Any rows written to the DB with the rising column value since the last read will be skipped.
Have you checked the datatime values of the lost rows?
--- If this reply helps you, an upvote would be appreciated.