Generative AI on Enterprise Cloud with NiFi and Milvus
Professional Recycling - SSIS Custom Control Flow Components With Visual Studio Community
1. Professional Recycling
SSIS Custom Control Flow Components
With Visual Studio Community
@wstrasser
Wolfgang Strasser
wolfgang.strasserATgmx.at
workingondata.wordpress.com
3. About me – Wolfgang Strasser
consultant
Software, Business Intelligence and DWH at cubido
Like to load, transform, modify and query data
SSIS & T-SQL
SSIS Users since SQL 2005
SSIS Custom Component developer > 6 years
4. Who knows or used/uses…
.. SSIS
.. SSIS Script Task
.. SSIS Custom Components
12. Dev Environment
Visual Studio
SSDT–BI (to develop SSIS Packages)
(SQL Server)
If you like to test the package deployed (SSIS Catalog)
C# knowledge (preferred)
Or any other .NET language
Admin Rights on Development machine
24. User Interface
Recommendation
separate assemblies for Task and UI
localization
Do not need UI @ server
Deployment
UI-assembly in GAC only
42. Be Professional – Automated Builds
Increment AssemblyFileVersion
Build for multiple SQL Server Versions
Build Configurations
Project File
43. Recycle Application logic
Reduce Copy&Paste errors
Reduce multiple programming efforts
Reuse logic…
.. written in one place
.. used in multiple places
Be professional - Be faster!
If you have questions, please contact me via twitter or e-mail!
The next topic I would like to talk about is the persistance of component settings. What I really think is desirable – is to have persistant component settings. You change the value of a settings, Hit Save in the SSIS Package and when you open up this package the next time, I want to see these values again.
Custom components already persist their settings into the underlying SSIS XML code – but if you want to implement your own persistence strategy OR if you have complex types of properties that need to be saved – the SSIS API provides these options.