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

Announcements
April 13–15 - Dare to Unleash a New Professional You at Qlik Connect 2026: Register Now!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

tMSSQLInput error

I'm using TOS for Big Data with third party additional packages and am moving data from a MS SQL Server DB to a PostgreSQL DB. So far, three jobs are working as expected with the following components: a tMSSqlConnection (using the default JDBC Provider) that always connects, a tMSSqlInput using the existing connection, a tPostgresqlOutput and a tMSSqlClose. Suddenly, new jobs with the same components are crashing and I can see on the Execution pane that it connects but then shows an error like this:
Batch entry 0 INSERT INTO "table_name" (all the fields I needs) VALUES (...) was aborted. Call getNextException to see the cause.
I thought it was the insert statement syntax because there were no single quotes on string, char or varchar values and if I copy the insert from the error and paste it into the tPostgrsqlOutput's SQL Builder window was also failing. So, I decide to add the quotes in tMSSqlInput 's select statement with the same results but now the insert statements from the displayed error works on tPostgrsqlOutput's SQL Builder window.
I'm not using Microsoft JDBC because last time I installed it ended up removing and reinstalling TOS for Big Data. Am I missing something?
Here is a screen shot of job that's failing.
 

Labels (2)
1 Reply
Anonymous
Not applicable
Author

Hi,
Has your data (73425 rows) been successfully loaded into your PostgreSQL DB? Could you please post your tMSSQLInput component setting screenshot into forum?
Best regards
Sabrina