Skip to content
English
  • There are no suggestions because the search field is empty.

Why Temp/Staging Tables Appear Empty and What they are used for

This article explains why our BI Connector and Database Integration apps can create many temporary (staging/audit) tables — often in a Temp schema — and why most of them may appear empty. It also covers how those tables are used, recommended handling, and basic troubleshooting steps you can follow.

 

Why does our app create temp/staging tables

  • Temp tables are created as part of the normal sync process to stage and validate data (especially associations) before it is pushed into the main tables.
  • The system performs a full refresh for certain syncs (notably association tables), which uses these intermediate Temp tables during the load.
  • The connector pulls all available objects from the source system; if a source object or feature is not used in the source system, the corresponding table in the destination will be created but remain empty.

Why most temp tables may be empty

  • If the corresponding object/feature isn’t used in the source system, the destination/staging table will exist but contain no rows.
  • Temp tables are used only during the staging/validation phase; after data is pushed to main tables, the temp tables may remain empty until the next appropriate sync runs.

Recommended handling and behavior

  • Do not delete Temp tables. They are required for normal operation and for the system to complete association syncs correctly.
  • If Temp tables are deleted (accidentally or intentionally), the next scheduled resync will recreate them automatically. However, recreating them adds unnecessary processing overhead.
  • The Temp schema and its tables are part of normal behavior and should be retained to avoid interruptions or extra work during scheduled loads.

How syncs and timing relate to Temp tables

  • Some syncs run as full-refresh cycles (associations are a primary example) and rely on Temp tables during that process.
  • Sync history for individual tables is tracked in a SyncHistory table in the dataset; it shows when each table initiated its scheduled resync in UTC. Use this to see when temp-table activity is expected.
  • Because resyncs are scheduled and executed one table at a time, initiation times may vary slightly between tables.

Troubleshooting steps when tables appear empty

  1. Confirm whether the source object/feature is being used in the source system:
    • If the source has no records for that object (for example, no Leads in the source), the corresponding destination table will remain empty until records exist.
  2. Compare source and destination data:
    • Provide full, uncropped screenshots showing the dataset table in your reporting tool and the corresponding data in the source portal to verify discrepancies.
  3. Allow scheduled resyncs to complete:
    • If a connection or authentication change occurred or a resync was queued, allow the scheduled resync(s) to complete before concluding data is missing.
  4. If Temp tables were deleted:
    • Expect them to be recreated automatically at the next scheduled resync; however, avoid deleting them to prevent unnecessary reprocessing.