Skip to main content
To homepage To homepage
Solved

Add Fabric LakeHouse as new source

  • December 9, 2024
  • 7 replies
  • 93 views
M
Starter

Hi All, I try to add my Fabric LakeHouse as a new source in TimeXtender version 20.10.50.64 but I keep getting an error when I try to read objects from datasource eventhough it says connection is succesfull.

Data source settings

I copy the SQL connection string from my lakehouse and put it as server name. When I do "Read object from data source” I get the following error. The weird thing is that when I try these exact same stept in SSMS I can see the table from the source with the data in it. Am I missing some steps?

 

Best answer by Thomas Lind

Hi ​@mikeschipper 

No need, we already know of the issue. There will be a fix. In the mean time

 

What I found out was that the ADO.net versions of our SQL data source providers worked fine. These are the ones we use for ODX and in the new TDI.
?name=image.png
 
Here is the connection string I use for ADO.
Data Source=123456789.datawarehouse.fabric.microsoft.com;Initial Catalog=TLDevLake;User ID=devtest@timextender.com;Authentication="Active Directory Password"
?name=image.png
Of course, you need to use the server and database you need to connect to instead.

You can also use OLE DB, but it must be the latest version of the provider.
?name=image.png
You can't use SQL Server Native Client 11.0. It doesn't work and you get the same error as the normal one.
 
Here is the connection string from it.
Provider=MSOLEDBSQL19;Data Source=123456789.datawarehouse.fabric.microsoft.com;User ID=devtest@timextender.com;Initial Catalog=TL_FAB_SQL;Authentication=ActiveDirectoryPassword
?name=image.png
 
This should work and you can convert your existing SQL data source to this without losing any mappings.

View original
Did this topic help you find an answer to your question?

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • rory.smith
  • TimeXtender Xpert
  • December 9, 2024

Hi,

 

you may have better luck using the MSOLEDBSQL19 driver with Active Directory Password authentication. Something has recently changed that stops things from working using the other connector.

M
Starter

Hi Rory,

 

Thank you for your response. Where can I find these settings? Do I still use the SQL Server data source? Can you help me with this, thanks in advance.

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • rory.smith
  • TimeXtender Xpert
  • December 9, 2024

Hi,

 

you should install the latest SQL Server OleDB driver and then use the AnyConnect source, there you can choose that driver to underly your connection.

M
Starter

Hi,

I tried these steps with the MSOLEDBSQL19 provider, but still got the same error when I do test connection. The connection is succesfull in SSMS this looks very weird to me. Do you know any other steps I can try?

 

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • rory.smith
  • TimeXtender Xpert
  • December 10, 2024

Hi,

it's probably easiest to log a support ticket in that case.

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • December 10, 2024

Hi ​@mikeschipper 

No need, we already know of the issue. There will be a fix. In the mean time

 

What I found out was that the ADO.net versions of our SQL data source providers worked fine. These are the ones we use for ODX and in the new TDI.
?name=image.png
 
Here is the connection string I use for ADO.
Data Source=123456789.datawarehouse.fabric.microsoft.com;Initial Catalog=TLDevLake;User ID=devtest@timextender.com;Authentication="Active Directory Password"
?name=image.png
Of course, you need to use the server and database you need to connect to instead.

You can also use OLE DB, but it must be the latest version of the provider.
?name=image.png
You can't use SQL Server Native Client 11.0. It doesn't work and you get the same error as the normal one.
 
Here is the connection string from it.
Provider=MSOLEDBSQL19;Data Source=123456789.datawarehouse.fabric.microsoft.com;User ID=devtest@timextender.com;Initial Catalog=TL_FAB_SQL;Authentication=ActiveDirectoryPassword
?name=image.png
 
This should work and you can convert your existing SQL data source to this without losing any mappings.

M
Starter

Hi Thomas,

Thank you for your response. The ADO.net works for me, I'm able to load the table in the ODX!

Reply


Most helpful members this week

Terms and ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings