Skip to main content
StickyTutorial

Using Fabric SQL Database as Storage for Prepare Instance

  • November 27, 2024
  • 3 replies
  • 294 views
Using Fabric SQL Database as Storage for Prepare Instance
JTreadwell
Employee
Forum|alt.badge.img+5

TimeXtender Data Integration can leverage Microsoft Fabric SQL Database as storage for your Prepare Instance, providing a fully managed, cloud-based data warehouse solution. This feature enables seamless integration with Microsoft Fabric's ecosystem while maintaining TimeXtender's powerful data transformation capabilities.

Why Use Fabric SQL Database?

  • Seamless integration with your Fabric Ecosystem
  • Database mirroring to Fabric OneLake
  • Fully managed database-as-a-service
  • Always running the latest SQL Engine
  • No patches or updates required
  • Automatic scaling capabilities
  • Read more: Fabric SQL Database decision guide | Microsoft Learn

Prerequisites in Fabric

Create a Fabric SQL Database
 

  1. Navigate to your Fabric Workspace
  2. Click + New item
  3. Scroll to Store Data section and select SQL database (preview)
  4. Enter a database name and click Create

Add an Admin User or Service Principal
 

  1. Navigate to your Fabric workspace
  2. Click Manage Access
  3. Select Add people or groups
  4. Enter the name or email:
    1. A Service Principal is recommended
    2. Non-MFA user/password is also supported
  5. Select Admin role from dropdown
  6. Click Add

Locate Connection Details
 

 

  1. Open the newly created SQL database in Fabric portal
  2. Click Settings (the blue gear icon in the left of the ribbon under the Home tab)
  3. Select Connection Strings
  4. Note the server name (between “Data Source =” and the first comma. Include the “,1433” but Exclude "tcp:")
  5. Note the database name (between "Initial Catalog=" and ";")

Configure TimeXtender

Configure your Prepare Instance

  1. Navigate to Instances in the TimeXtender Portal
  2. Click Add Instance > Add prepare instance
  3. Configure General Settings:
    • Enter the Instance name
    • Select SQL Server as Server storage type
  4. Configure SQL Server Settings:
    • Enter Server name from connection string
    • Enter Database name from connection string
    • Select Authentication Type:
      • Microsoft Entra Service Principal (Recommended)
      • Microsoft Entra Password Authentication (Must be Non-MFA user)
    • Enter username and password of a User or Service Principal with Admin Permissions
  5. Validate Connection:
    • In TimeXtender Data Integration interface, refresh your instances
    • Identify your newly created instance and double click on it to open the instance
    • Right-click on the instance and select Edit Instance
    • Click Test Storage Connection

Troubleshooting

Invalid Cast Exception Error

When executing a table in the Prepare instance you receive this error:

Exception Type: System.Exception
Message: Data processing faulted
.....
Inner Exception:
     Exception Type: System.InvalidCastException
     Message: Specified cast is not valid.
          Stack Trace: at DataStorageEngine.Fabric.FabricDiscoveryHubExecution.<>c__DisplayClass25_0.<ReadData>b__0(DataColumn[] dataColumns, Int64 rowCount, ParquetColumnGroup dummy_group) at ODX.Parquet.ParquetDataDownloader.ProcessData(Action`3 onDataAvailable)

This error occurs when your Ingest Lakehouse Parquet files were created using the Spark Runtime Version 1.3. These Parquet files store date and timestamps in a different format that’s not directly supported by Fabric Databases. However, creating the Parquet files using the Spark Runtime 1.2 fixes the issue. 

Follow these steps to resolve:

  1. Navigate to the Fabric workspace and click Workspace settings
  2. Expand Data Engineering/Science and select Spark settings
  3. Click on the Environment tab
  4. Set Runtime Version to 1.2 (Spark 3.4, Delta 2.4)
  5. Click Save
  6. If you previously created Ingest Lakehouse using runtime v1.3, you need to run a full load transfer task for your data sources after changing to 1.2. Alternatively delete the tables in your lakehouse and run the transfer tasks for your data sources again.

Fabric capacity paused

If you encounter errors similar to below please start your Fabric capacity in the Azure portal

 

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

3 replies

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • 1051 replies
  • November 27, 2024

If you do not want to use Microsoft Entra Password Authentication you are able to use 

Microsoft Entra Service Principal authentication as well.

You need to be sure the app is added in the Manage Access part of the workspace similar to the other option shown.
 

 


rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • TimeXtender Xpert
  • 674 replies
  • April 16, 2025

Hi,

 

in a change to how Fabric works you now seem to need to include ",1433” in the server name parameter to get Fabric SQL to work as a Prepare engine.


rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • TimeXtender Xpert
  • 674 replies
  • April 17, 2025

I tried to generate the exact error you get, but it looks like after you have a successful run the problem does not occur again and you can have the ,1433 included or not. The error you may encounter looks something like: “Service Principal xxx cannot be found in Tenant yyy” even though that user certainly does exist in Entra.


Reply


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