Input tool vs Dynamic Input tool Performance

Does anyone know if there is a performance difference between an input tool and a dynamic input?

I have a huge number of input tools that are getting pointed at one db schema but will likely need to change to a different schema when put into prod. Im trying to think of an easy way to make that change across all of the inputs by just changing one location.

Input

Accepted answers

mceleavey

Hi @paul_houghton ,

it's pretty much insignificant, but is another call to a folder location, and if you're looping through millions of those then it will have an impact on performance, but it would still be small.

All comments

mceleavey

Hi @paul_houghton ,

Dynamic Input will be slightly slower than Input simply because it needs to read in templates, but for this you don't need to use it.

You can wrap the input in a batch macro and simply feed the connection string in as a control parameter. You could then put this in an app which would allow the user to select the schema at runtime, or you create is a constant and have it determined automatically at runtime.

There are a few approaches here depending on your needs.

paul_houghton

The macro option would have been my next option. I would ask first, if the template is just a single line template, how significant is the template loading process? Because I will be handing it to another team to maintain, simpler would be better as long as the performance isn't significant.

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703