Forum Discussion

debiagui's avatar
debiagui
Resolver I
11 months ago
Solved

Fails to Sync SQL database to SQL endpoint

We’ve been working with a SQL database for the last few months. Today, as usual, we inserted new rows into a table, but even after waiting 5 hours, those rows are still not appearing in the SQL endpo...
Need Help
debiagui's avatar
debiagui
Resolver I
11 months ago

Hi Poojara_D12 yes please can you guide me to the lasted know issues?

I created a new dabase and replicate all data and again fails to update sql endpoint, seems like is a know issue.

My tables are normal, no custom column, or any extrange index logic  

 

 

  • v-sgandrathi's avatar
    v-sgandrathi
    Community Support
    11 months ago

    Hi debiagui,

     

    We recognize your concern regarding the SQL endpoint not updating even after creating a new database and replicating the data. Currently, this is a known limitation, as synchronization between Lakehouse data and the SQL endpoint may take longer than anticipated. Factors such as the number of tables, partitioning structure, and delta log files within Lakehouse can contribute to these delays.

    To address this, users have found that waiting approximately 10–15 minutes after loading data before querying the SQL endpoint often ensures that new rows are visible.
    Additionally, Microsoft has introduced a documented “Refresh SQL Endpoint Metadata” REST API, which can be called programmatically post-ingestion to trigger synchronization and monitor its completion status, thereby improving reliability.

    We also suggest implementing best practices like vacuuming or checkpointing delta tables, especially in environments with substantial partitions or large logs, as these steps can help maintain consistent synchronization times.

     

    Thank you.

    • debiagui's avatar
      debiagui
      Resolver I
      11 months ago

      Hi v-sgandrathi the issue is with the data in the SQL database versus the data in the SQL endpoint of the same database. I created a new database and replicated the schema without any indexes, relationships, or special columns—just varchar, integer, and long fields—but the SQL endpoint does not show any tables.

      • v-sgandrathi's avatar
        v-sgandrathi
        Community Support
        11 months ago

        Hi debiagui,

         

        Thank you for providing the additional information. If the SQL endpoint is not displaying any tables, even after creating a new database with a basic schema, this likely indicates a metadata registration issue rather than just a problem with row synchronization.

        To address this, please consider the following steps:

        • Confirm that your tables are registered in the Lakehouse view under the Tables section. If they appear only as files and are not promoted to tables, they will not be visible in the SQL endpoint.

        • Use the Refresh SQL Endpoint Metadata REST API to manually refresh the schema. This can help in cases where new tables are not automatically recognized by the endpoint.

        • Verify that your database is created within a Fabric-enabled workspace and that the SQL endpoint feature is active. Workspaces without Fabric support will not expose schema in the SQL endpoint.

        • Since you have already checked the schema, please also review the Microsoft Fabric Known Issues page or your tenant’s Service Health dashboard for any ongoing SQL endpoint incidents.
        Fabric known issues - Microsoft Fabric | Microsoft Learn

         

        Thank you.