Skip to main content
To homepage To homepage

We are experiencing a small issue with one of the connectors while using managed queries. When I use the query tool, we are utilizing the SQL endpoint from a Fabric Lakehouse to retrieve the data into the ODX. When I query the DBO table, I receive 12 records. For example, when running this query:

SELECT [SinkCreatedOn],
        SinkModifiedOn],
       Âomoperatingunitnumber],
       >modifieddatetime],
       bmodifiedby],
       ycreateddatetime],
       ecreatedby],
       cdataareaid],
       Ârecid],
       Âtableid],
       /createdon],
       rmodifiedon],
       ,IsDelete]
  FROM dbo.oomoperatingunit]
 

I also get 12 records. However, when we transfer this managed query, we only receive 11 records. This issue has occurred with multiple tables. We are not applying any filters to this dataset.

Do you have any idea why this might be happening? Manually excluding or including all the columns is not manageable on the scale we are working with, so we rely on writing managed queries.

Hi @Bernarddb ,

which connector are you using to connect? In theory, you should be able to use OleDB (make sure you have the most recent drivers installed on TX machines: https://learn.microsoft.com/en-us/sql/connect/oledb/oledb-driver-for-sql-server), ODBC and others. I expect you should be able to treat a SQL Analytics endpoint as if it were SQL Server being called with read-only intent.

I wonder if all connectors result in the same result or whether it is limited to one or more. If you run a COUNT (*) FROM table Table Query, does it return 12 or 11?

 

@rory.smith 

 we are currently using 

When i use the count(*) it returns 12. and that's the same number of rows i receive if i use the normal dbo transfer.

Hi @Bernarddb,

maybe if you install the most recent SQL Server OleDB drivers and try Microsoft OLE DB Driver for SQL Server the result will be different? At least the count shows you that it is not some kind of rights situation with respect to the credentials Ingest is using to extract the data from Fabric.

So something is either going wrong in general, or with the TX SQL source specifically. If the Microsoft OLE driver shows the same behaviour that may help narrowing down where the problem lies. I suspect it is support ticket time regardless though.

I'm going to create a Support ticket. Will update if we have an outcome

Reply


Terms and ConditionsCookie settings