Read Uncommitted in SQL Query Text

Brendan Codrington shared this question 2 months ago
Answered

Hi,

If we have a connection set as read uncommitted in its isolation level settings, should we see that reflected in the SQL query text at the database level?

Thanks,

Brendan

Comments (3)

photo
1

Hi Brendan,

Ultimately at some point Yellowfin is going to run a query similar to the one below (depending on your database type):

set transaction isolation level  read committed 
This should only appear when the Source is first validated or refreshed (not on each query being sent). This query will not be in the logs but if your DB has an SQL History module (SQL Server uses SQL Profiler for this, Postgres can log all queries to their logs, etc) then it should show up.

It would be great to understand the use case behind your question, in case there is something more we can do to help here.

Cheers,

Neal

photo
1

Hi Neal,

Thanks for the info. We were experiencing some long running queries on reports that hadn't previously done so after upgrading the server to MSSQL Server 2019 on Windows 2019 so were trying to isolate potential causes, including whether yellowfin was waiting for data to be locked before it would return the query. Once we confirmed we had it set as read uncommitted we were then looking for that in the query text.

I'll close this ticket unless we have any more questions related to this!

Thanks again,

Brendan

photo
1

Hi Brendan,

Glad we could help and do keep us updated with your progress as it would be good to understand the cause here.

Cheers,

Neal