Azure Data Explorer
An Azure data analytics service for real-time analysis on large volumes of data streaming from sources including applications, websites, and internet of things devices.
482 questions
Why does the ODBC driver return an extra "ROWSTAT" column when connected to a Azure Data Explorer (*.kusto.windows.net)?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 25%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKS%3C/text%3E%3C/svg%3E)
Kevin Seekell
1
Reputation point
We are using ODBC Driver 17 for SQL Server to connect to Azure Data Explorer (*.kusto.windows.net). We use SQLExecDirect to execute a query such along the lines of "SELECT col1 from table". We expect the result to only contain 1 column. However, a later call to SQLNumResultCols indicates that there are actually 2 columns in the result. The second column is called "ROWSTAT" and appears to have a value of 1 in every row. I couldn't find much about "ROWSTAT" online other that it is supposed to be a hidden column. Every query we run against the server includes this extra column. Could someone provide an explanation about why this could be appearing, and how to prevent it from appearing in our results? This behavior is problematic for applications that expect the amount of returned columns to match the number of columns requested.
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 70%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
MartinJaffer-MSFT 26,031 Reputation points2021-03-01T21:35:56.017+00:00 Hello @Kevin Seekell and welcome to Microsoft Q&A.
Information on "ROWSTAT" does seem sparse. From what I can piece together, "ROWSTAT" is generated when the cursor is fetching records into a buffer and tracks whether present or missing. Given that ROWSTAT is present in every query you do, it is probably involved in the transport of data.
I suspect the SQLNumResultCols ignores whether columns are hidden or not.Please confirm you are not using cursors, and I will inquire internally for more information.
-
Kevin Seekell 1 Reputation point
2021-03-03T15:01:28.163+00:00 Hi @MartinJaffer-MSFT ,
Thank you for looking into this. I can confirm that we we are not using cursors. Please let me know what you find.
-
MartinJaffer-MSFT 26,031 Reputation points
2021-03-10T18:43:55.8+00:00 @Kevin Seekell
I heard back. The ROWSTAT is being generated by the ODBC driver. I will let you know more as I have it. -
Kevin Seekell 1 Reputation point
2021-03-12T18:23:01.433+00:00 Thanks for the update Martin. We'd be interested to know if there is a way to prevent ROWSTAT from being generated.
-
Kevin Seekell 1 Reputation point
2021-03-24T15:13:37.03+00:00 Hi Martin,
Do you have any updates on this?
Sign in to comment