When running any query against SQL Server using "Splunk DB Connect" I see that the query always executed 4 times instead of just one. Only result of the 3rd execution is returned and displayed to the client. This behavior can be easily verified either by using SQL Server Profiler or by running this query:
IF OBJECT_ID('dbo.TESTTABLE') IS NULL
BEGIN
CREATE TABLE dbo.TESTTABLE(id int)
INSERT dbo.TESTTABLE(id) VALUES(1)
END
SELECT * FROM dbo.TESTTABLE
UPDATE dbo.TESTTABLE SET id = id + 1
I would expect the result to be "1" but I see "3" instead. Next execution will return 7, 11, 15 and so on, instead of 1,2,3...
I don't see why it's necessary and would consider it as a major bug. Running very expensive queries against production databases takes a lot of resources already but running it 4 times takes precisely 4 times more resources. That's simply unacceptable.
Splunk Version ............................................7.2.0
Splunk Build ............................................8c86330ac18
Current Application: Splunk DB Connect
App Version ............................................3.1.3
App Build ............................................55
↧