Add a data flow task with Excel Source to point to Excel file and ADO Recordset destination to point to object variable.
Then use a For Each Loop to loop through ADO .NET recordset and then use individual variable to hold servername,dbname etc. If tables are all the same structure then you can use same data flow for data transfer else you need to use separate data flow one for each table.
------------------------------------------------------------------------------------------------------ SQL Server MVP http://visakhm.blogspot.com/
Add a data flow task with Excel Source to point to Excel file and ADO Recordset destination to point to object variable.
Then use a For Each Loop to loop through ADO .NET recordset and then use individual variable to hold servername,dbname etc. If tables are all the same structure then you can use same data flow for data transfer else you need to use separate data flow one for each table.
------------------------------------------------------------------------------------------------------ SQL Server MVP http://visakhm.blogspot.com/
Hi Visak
Thanks for you reply. Is it possible to make this overall process a dynamic process. For instance if i update Excel file with new tables and then i would have to add a new data flow task to the solution (not so much of work), any thoughts around making it dynamic so that the support gusy update the file and let the SSIS package do the rest ?
Add a data flow task with Excel Source to point to Excel file and ADO Recordset destination to point to object variable.
Then use a For Each Loop to loop through ADO .NET recordset and then use individual variable to hold servername,dbname etc. If tables are all the same structure then you can use same data flow for data transfer else you need to use separate data flow one for each table.
------------------------------------------------------------------------------------------------------ SQL Server MVP http://visakhm.blogspot.com/
Hi Visak
Thanks for you reply. Is it possible to make this overall process a dynamic process. For instance if i update Excel file with new tables and then i would have to add a new data flow task to the solution (not so much of work), any thoughts around making it dynamic so that the support gusy update the file and let the SSIS package do the rest ?
Thanks Heaps
Select Knowledge from LearningProcess
Its not a problem adding new rows to excel so far as the metadata (columns) does not change.
But for actual data flow you've to have as many data flow paths as tables so long as tables have different structure. SSIS cant change metadata at runtime
------------------------------------------------------------------------------------------------------ SQL Server MVP http://visakhm.blogspot.com/
If Dat flow task could have changed the meta data dynamically , it would have made SSIS more strong.
Thanks for you help my friend :)
Cheers
Select Knowledge from LearningProcess
Thats against the basic ETL assumption which assumes source to be fixed. Any changes that have to done has to be preset by means of transformations in data flow and it cant vary at runtime
------------------------------------------------------------------------------------------------------ SQL Server MVP http://visakhm.blogspot.com/