Need to create an SSIS Package for users to directly modify a table -
i need allow couple of users modify table in database, preferably part of integrated package submits changes our live database.
please allow me explain further:
we have automated import task 1 database system another, data transformation on way through.
as part of task, various checks run before final import , rows incomplete or incorrect data sent rejections table , deleted import table.
i need allow couple of senior users ability view , correct missing/incorrect entries rejection table, before re-staging , submitting live database. (obviously, re-checked before submission , re-rejected if still wrong).
can tell me need in ssis display contents of specific table (e.g. mydatabase.dbo.reject_table) user running package local pc (the package will, of course, located on server).
then need ability modify contents of table - either 1 row @ time or en-masse. not bothered which).
when done, hit "continue" or "next" type button, continues run remainder of package, more comfortable writing.
it interactive stage(s) struggling , appreciate advice.
thanks craig
that non-native functionality in ssis.
you can write pretty want in script task , includes gui components. (i once had package play music). in data flow, have script component edits each row passing through component.
why bad idea
suitability - isn't ssis for. biggest challenge you'll run data flow tightly bound shape of data. reject table customer different reject table phone.
cost - how going allow senior users run ssis packages? if answer involves installing ssis on machines, looking production license sql server. that's 8k 23k ish per socket sql server 2005-2008r2 , insane per core sql server 2012+.
what better approach
as always, decompose problem smaller tasks until can solve it. i'd make 2 problem statements
- as data steward, need ability correct (edit) incomplete data data can imported our application.
- as x, need ability import (workflow) corrected rejected data can bill our customers (or whatever reason is).
editing data. i'd make basic web page or thick client app provide edit capability. datagridview 1 way of doing. heck, forgo custom development , slap access front end tables , let them edit data through that.
import corrected data. i'd use ssis possibly not exclusively. i'd @ adding column reject tables indicates whether it's ready reprocessing. each reject table, i'd have package looks rows flagged ready. i'd use delete first pattern remove flagged data , either insert production tables or route reject table further fixing. mechanism launching packages whatever makes sense. since i'm lazy,
- i'd have sql agent job runs packages ,
- create stored proc can start job
- grant security on stored proc data stewards
- provide stewards big red button says
import
how that's physically implemented depend on how solved edit question.
Comments
Post a Comment