Reputation: 512
I have a case where I get X rows of database names as parameter which I need to connect to. I've succesfully made the job and transformations to repeat a table input step for each database name given as parameter. So this all works nicely when those dbnames happen to be valid. But if one of those names is invalid (db does not exist with given name), then the table input step fails with an error and the whole job stops instead of continuing for the rest of the names that are valid.
So I'm wondering is there a way to validate whether database connection parameters are valid or not? And maybe skip the step when an invalid database parameters are found?
Upvotes: 3
Views: 3757
Reputation: 492
Parameterize the database name for your connection, then use a Check DB Connections job entry to test the the connection. I would imagine that this would require a chain of 2 transformations and 1 job:
Maybe look into this answer for help using variables in DB connections.
Good luck!
Upvotes: 3