ETL and Data Integration tools - Modern ETL software for everyone

Hi. I've been trying to evaluate your Visual Importer Enterprise product and have a few of questions:

1) Without thinking, I installed your product a week before I went on a two-week vacation. Now that I'm back and trying to continue my evaluation, I find I've only got two days left on the license. Is there any way I could get an additional 3 weeks demo license?

2) Can you think of any way within V.I. that the Source database can be defined at run time? We have the situation where we would like to poll a number of database servers, collecting their individual information into one master DB. However, the pool of servers is dynamic, so we don't know which ones we need to connect to until we're ready to run the import scripts. I know I could create a package with an ODBC connection object for every possible server, but that could lead to an administrative nightmare.

3) If I check the option for executing packages in a separate thread, and have multiple items scheduled, will each 'runnable' item start up in its own thread concurrently, or does one execution agent (Windows Service) only run one 'job' at a time?

Thanks for your time,

Rick

1) Without thinking, I installed your product a week before I went on a two-week vacation. Now that I'm back and trying to continue my evaluation, I find I've only got two days left on the license. Is there any way I could get an additional 3 weeks demo license?

>>> Drop us an email and we will send you a key to extend evaluation period.

2) Can you think of any way within V.I. that the Source database can be defined at run time? We have the situation where we would like to poll a number of database servers, collecting their individual information into one master DB. However, the pool of servers is dynamic, so we don't know which ones we need to connect to until we're ready to run the import scripts. I know I could create a package with an ODBC connection object for every possible server, but that could lead to an administrative nightmare.

>>> It is not straight forward but possible by using system variables

3) If I check the option for executing packages in a separate thread, and have multiple items scheduled, will each 'runnable' item start up in its own thread concurrently, or does one execution agent (Windows Service) only run one 'job' at a time?

>>> It only runs one job at the time

Peter