powershell - Best approach to build reusable C# data integration assemblies -
How have you addressed issues while creating a reusable suite of data integration assemblies? We are using a Microsoft Store SQL Server and C # we are consolidating our DB integration code into many C # assemblies. In this we are killing many common problems
-
We like the source / destination of SSIS and GUI is the flexibility, but this environment only (easily) cut / paste reuse Supports - unless you know differently.
-
We can create (console) applications that use standard command line parameters and / or config files. In this way we can bat normal tasks, but we do not have a GUI.
-
If we code the normal GUI to work with our standard parameters, then we again create the area of SSIS.
-
We can use our C # assemblies through an electric shell cover. However, PowerShell is great for developers / administrators but not the user and we are hearing that it is slower than the SSIN equivalent, and we press the GUI issue again.
Our typical integration task will take information from 2 different database sources and a flat file, implement some (in fact) complex logic and then a third database will update.
Comments
Post a Comment