EricWhitley
7 years agoQrew Trainee
Any interest in an open source set of SSIS components for MSSQL?
Hello -
Wondering if there are other users of Microsoft SQL Server who might be interested in a simple set of SSIS components (connection manager, data source, and data destination)?
I realize there's a commercial ODBC driver out there (which looks great), but I found myself in an odd situation where, for specific reasons, buying software is off the table, but investing time is OK.
I've already got some basic stuff working and my intent is to polish it up enough to be useful without needing to know the API:
For the data source I'm also going to add something I've found useful on other projects, which is emitting "maybe kinda close enough DDL" for generating your target tables (it just abuses SMO). I've already got this working and it applies some basic rules (sanitizing column names, prefacing the individual address fields with the parent name prefix, etc.) as well as does some very rudimentary guesses on data types. It's mean to be an assist, not an operation you completely trust.
I already wrote a generalized "auto sync" process that says "get everything from a database" (simple C# app - creates and runs DDL, merges data over, etc.), but I'm in the process of taking subsets of that and putting things into simple SSIS components. Basic SSIS process - set up the connection manager with your API key and select the database, then in the data source, choose your table. That's it. Done. It's meant to be easy.
The only "API-ish" bit I'm exposing (mainly because I'm lazy) is the query. For right now I'm planning on that just being a string you enter. (EX: https://help.quickbase.com/api-guide/index.html#samplequeries.html) I don't want to have to get too far into the weeds right now in building a custom UI for that.
I'm currently testing on SQL 2016.
If anyone else is interested in testing later, please let me know. I'm happy to ship out a sample DLL. Right now I've got the data source implemented as I try to figure out how MS wants the destination written.
Code will eventually get to GitHub once I finish wrapping some basic UI elements around things.
Thank you,
Eric
Wondering if there are other users of Microsoft SQL Server who might be interested in a simple set of SSIS components (connection manager, data source, and data destination)?
I realize there's a commercial ODBC driver out there (which looks great), but I found myself in an odd situation where, for specific reasons, buying software is off the table, but investing time is OK.
I've already got some basic stuff working and my intent is to polish it up enough to be useful without needing to know the API:
- Connection manager for attaching
- Data source for querying
- Data destination for writing back
For the data source I'm also going to add something I've found useful on other projects, which is emitting "maybe kinda close enough DDL" for generating your target tables (it just abuses SMO). I've already got this working and it applies some basic rules (sanitizing column names, prefacing the individual address fields with the parent name prefix, etc.) as well as does some very rudimentary guesses on data types. It's mean to be an assist, not an operation you completely trust.
I already wrote a generalized "auto sync" process that says "get everything from a database" (simple C# app - creates and runs DDL, merges data over, etc.), but I'm in the process of taking subsets of that and putting things into simple SSIS components. Basic SSIS process - set up the connection manager with your API key and select the database, then in the data source, choose your table. That's it. Done. It's meant to be easy.
The only "API-ish" bit I'm exposing (mainly because I'm lazy) is the query. For right now I'm planning on that just being a string you enter. (EX: https://help.quickbase.com/api-guide/index.html#samplequeries.html) I don't want to have to get too far into the weeds right now in building a custom UI for that.
I'm currently testing on SQL 2016.
If anyone else is interested in testing later, please let me know. I'm happy to ship out a sample DLL. Right now I've got the data source implemented as I try to figure out how MS wants the destination written.
Code will eventually get to GitHub once I finish wrapping some basic UI elements around things.
Thank you,
Eric