ezapi

Warning messages with EZAPI EzDerivedColumn and input columns

徘徊边缘 提交于 2019-12-11 10:32:25
问题 When adding a derived column to a data flow with ezAPI, I get the following warnings "Add stuff here.Inputs[Derived Column Input].Columns[ad_zip]" on "Add stuff here" has usage type READONLY, but is not referenced by an expression. Remove the column from the list of available input columns, or reference it in an expression. I've tried to delete the input columns, but either the method is not working or I'm doing it wrong: foreach (Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSInputColumn100

What is the EzAPI equivalent for using an OLE DB Source command from variable?

与世无争的帅哥 提交于 2019-12-10 02:56:17
问题 tl;dr What is the EzAPI code to use an OLE DB Source with data access mode of "SQL command from variable" and assign a variable? Preamble Once a month, we need to refresh our public test site with subsets of production data. We have determined that for our needs, an SSIS solution provides the best fit for accomplishing this task. My goal is to systematically build a large number (100+) of "replication" packages. EzAPI is a friendly wrapper to the SSIS object model and it seems like a great

Automatically mapping columns with EZApi with OLEDBSource

六月ゝ 毕业季﹏ 提交于 2019-12-08 07:51:09
问题 Using EZApi, an EzOleDbSource object is created, and assigned the Table property. Another task is added (EzDerivedColumn) and attached to the EzOleDbSource object. When I open the package, I need to click on the OLEDB source to get the column output to the input of the derived task. Is there a way to programatically set the input and output mappings using EzApi? Note: I am using LinkAllInputsToOutputs(); Code: EzSqlOleDbCM RefConn = new EzSqlOleDbCM(package, dataVault_ConMgr); EzOleDbSource

What is the EzAPI equivalent for using an OLE DB Source command from variable?

家住魔仙堡 提交于 2019-12-05 02:41:03
tl;dr What is the EzAPI code to use an OLE DB Source with data access mode of "SQL command from variable" and assign a variable? Preamble Once a month, we need to refresh our public test site with subsets of production data. We have determined that for our needs, an SSIS solution provides the best fit for accomplishing this task. My goal is to systematically build a large number (100+) of "replication" packages. EzAPI is a friendly wrapper to the SSIS object model and it seems like a great way to save mouse-clicks. I would like for my packages to look like Variable - "tableName"; [Schema].