Why is there a gap in my database IDs?

Problem

Users may notice gaps in sequential database ID numbers when importing data using the Report Writer Data Import tool. This can cause confusion as it appears that some ID numbers have been skipped or lost.

Typical Cause

The Data Import tool processes data in a structured sequence. When the tool runs, it temporarily creates property records and assigns them database ID numbers sequentially. This process helps the system identify and check for errors before permanently adding new records.

However, these temporary records are automatically deleted once the error-checking process is complete.

When the user proceeds to import data, the system continues assigning new database IDs from the last available number, leading to a gap in the sequence where the temporary records were removed.

Less Typical Cause

On rare occasions, a gap in database ID numbers may occur in the instance of the database server going down. If the server experiences an unexpected shutdown or failure a jump in ID#s assigned is seen.

Solution

Understanding and Accepting ID Gaps

• These gaps are expected behavior and do not indicate missing or lost data.

• Users can verify the total number of imported records to ensure accuracy rather than relying on sequential IDs.

Rechecking Imports

• Run a comparison between the imported data and the original file to confirm all records are accounted for.

• Use search functions within Report Writer to confirm that all expected properties are present.

Additional Notes

• If significant gaps are noticed beyond expected behavior (e.g., large sequences of missing IDs), check for import errors or failed uploads.

• Users concerned about missing data should cross-check import logs or review error messages provided by the tool.

• For further assistance, contact support with details of the import, including file uploaded & upload results file if received.