Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
JGRFCU
Contributor II
Contributor II

Replicate full load task only load partial data set

We have a daily full load task from a SQL Server view to Snowflake that ran successfully but did not load the full dataset. We were expecting 700k records and only 400k loaded. There are no error or warning messages and nothing in the task logs that looked suspicious. We reran the task, and the table loaded all of the records.  This is the second time we have caught this issue. 

There have been no modifications to the view or the task. Because it is a view and not a table, there are no statistics available. It is not an indexed view.  From the task logs, we see that the SOURCE_UNLOAD has the incorrect number of rows sent from SQL Server.

Has anyone else experience this before?  What could be causing this?

2 Replies
DesmondWOO
Support
Support

Hi @JGRFCU ,

Thank you for reaching out to the Qlik Community.

Please check the following items:

  1. Any filters applied in the task.
  2. Enable verbose logging on SOURCE_UNLOAD and verify if the SQL statement is correct.
  3. In the task log, review the actual number of records that have been sent and received. For example,

    [SOURCE_UNLOAD ]I: Unload finished for table 'dbo'.'test01' (Id = 1). 1 rows sent.
    [TARGET_LOAD ]I: Load finished for table 'dbo'.'test01' (Id = 1). 1 rows received. 0 rows skipped. Volume transferred 400.

If root cause still can't be identified, please submit a support ticket.

Regards,
Desmond

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
narendersarva
Support
Support

@JGRFCU 

Sometimes it may not throw error or warnings in the task logs. Check the replicate repserv logs and sql server logs for the missing records on that date.

Also, confirm that the SQL Server is using the latest ODBC driver version.

 

Thanks
Naren