Action objects represent actions that are stored on the Analysis Services cube and executed by client applications such as Microsoft Excel.

AstAdfActivityNode is the abstract base type for all Azure Data Factory Activities.

AstAdfAzureBlobDatasetNode objects correspond directly to Azure Blob datasets in Azure Data Factory.

AstAdfAzureDataLakeDatasetNode objects correspond directly to Azure Data Lake Store datasets in Azure Data Factory.

AstAdfAzureDataLakeLinkedServiceNode objects correspond directly to Azure Data Lake Store linked services in Azure Data Factory.

AstAdfAzureDocumentDbDatasetNode objects correspond directly to Azure DocumentDB datasets in Azure Data Factory.

AstAdfAzureDocumentDbLinkedServiceNode objects correspond directly to Azure DocumentDB linked services in Azure Data Factory.

AstAdfAzureSqlDatabaseDatasetNode objects correspond directly to Azure SQL Database datasets in Azure Data Factory.

AstAdfAzureSqlDatabaseLinkedServiceNode objects correspond directly to Azure SQL Database linked services in Azure Data Factory.

AstAdfAzureSqlDataWarehouseDatasetNode objects correspond directly to Azure SQL Data Warehouse datasets in Azure Data Factory.

AstAdfAzureSqlDataWarehouseLinkedServiceNode objects correspond directly to Azure SQL Data Warehouse linked services in Azure Data Factory.

AstAdfAzureStorageLinkedServiceNode objects correspond directly to Azure Storage linked services in Azure Data Factory.

AstAdfAzureTableDatasetNode objects correspond directly to Azure Table datasets in Azure Data Factory.

AstAdfCopyActivityNode objects correspond directly the Copy activity in Azure Data Factory, which is referred to by the type 'Copy'.

AstAdfDataFactoryNode objects correspond directly to Azure Data Factories.

AstAdfDatasetNode is the abstract base type for all Azure Data Factory Datasets.

AstAdfDb2DatasetNode objects correspond directly to on-premises or IaaS DB2 datasets in Azure Data Factory.

AstAdfDb2LinkedServiceNode objects correspond directly to on-premises or IaaS DB2 linked services in Azure Data Factory.

AstAdfDotNetActivityNode objects correspond directly the custom activity in Azure Data Factory, which is referred to by the type 'DotNetActivity'.

AstAdfFileSystemDatasetNode objects correspond directly to on-premises or IaaS File System datasets in Azure Data Factory.

AstAdfFileSystemLinkedServiceNode objects correspond directly to on-premises or IaaS File System linked services in Azure Data Factory.

AstAdfHadoopStreamingActivityNode objects correspond directly the Hadoop Streaming activity in Azure Data Factory, which is referred to by the type 'HDInsightStreamingActivity'.

AstAdfHdfsDatasetNode objects correspond directly to on-premises or IaaS Hadoop Distributed File System (HDFS) datasets in Azure Data Factory.

AstAdfHdfsLinkedServiceNode objects correspond directly to on-premises or IaaS Hadoop Distributed File System (HDFS) linked services in Azure Data Factory.

AstAdfHiveActivityNode objects correspond directly the Hadoop Hive activity in Azure Data Factory, which is referred to by the type 'HDInsightHive'.

AstAdfLinkedServiceNode is the abstract base type for all Azure Data Factory Linked Services.

AstAdfMachineLearningBatchActivityNode objects correspond directly the Azure Machine Learning web service Batch Execution activity in Azure Data Factory, which is referred to by the type 'AzureMLBatchExecution'.

AstAdfMapReduceActivityNode objects correspond directly the Hadoop MapReduce activity in Azure Data Factory, which is referred to by the type 'HDInsightMapReduce'.

AstAdfMySqlDatasetNode objects correspond directly to on-premises or IaaS MySQL datasets in Azure Data Factory.

AstAdfMySqlLinkedServiceNode objects correspond directly to on-premises or IaaS MySQL linked services in Azure Data Factory.

AstAdfODataDatasetNode objects correspond directly to OData datasets in Azure Data Factory.

AstAdfODataLinkedServiceNode objects correspond directly to OData linked services in Azure Data Factory.

AstAdfOdbcDatasetNode objects correspond directly to on-premises or IaaS ODBC datasets in Azure Data Factory.

AstAdfOdbcLinkedServiceNode objects correspond directly to on-premises or IaaS ODBC linked services in Azure Data Factory.

AstAdfOracleDatasetNode objects correspond directly to on-premises or IaaS Oracle datasets in Azure Data Factory.

AstAdfOracleLinkedServiceNode objects correspond directly to on-premises or IaaS Oracle linked services in Azure Data Factory.

AstAdfPigActivityNode objects correspond directly the Hadoop Pig activity in Azure Data Factory, which is referred to by the type 'HDInsightPig'.

AstAdfPipelineNode objects correspond directly to pipelines in Azure Data Factory.

AstAdfPostgreSqlDatasetNode objects correspond directly to on-premises or IaaS PostgreSQL datasets in Azure Data Factory.

AstAdfPostgreSqlLinkedServiceNode objects correspond directly to on-premises or IaaS PostgreSQL linked services in Azure Data Factory.

AstAdfRootObjectNode is the abstract base type for all Azure Data Factory assets that can be defined at the root level of a Biml file.

AstAdfSimpleLinkedServiceBaseNode is the abstract base class for all Azure Data Factory linked services that are configured primarily with a connection string property.

AstAdfSqlServerDatasetNode objects correspond directly to on-premises or IaaS SQL Server datasets in Azure Data Factory.

AstAdfSqlServerLinkedServiceNode objects correspond directly to on-premises or IaaS SQL Server linked services in Azure Data Factory.

AstAdfSqlServerStoredProcedureActivityNode objects correspond directly the SQL Server Stored Procedure activity in Azure Data Factory, which is referred to by the type 'SqlServerStoredProcedure'.

AstAdfSybaseDatasetNode objects correspond directly to on-premises or IaaS Sybase datasets in Azure Data Factory.

AstAdfSybaseLinkedServiceNode objects correspond directly to on-premises or IaaS Sybase linked services in Azure Data Factory.

AstAdfTeradataDatasetNode objects correspond directly to on-premises or IaaS Teradata datasets in Azure Data Factory.

AstAdfTeradataLinkedServiceNode objects correspond directly to on-premises or IaaS Teradata linked services in Azure Data Factory.

AstAdfWebTableLinkedServiceNode objects correspond directly to Web Table linked services in Azure Data Factory.

AstAdfWebTableDatasetNode objects correspond directly to Web Table datasets in Azure Data Factory.

The ADO.NET connection connects to a data source that can be accessed via a .NET Framework data provider.

The ADO.NET destination loads data into a ADO.NET-compliant database that uses a database table or view.

The ADO.NET Source reads data from a ADO.NET-compliant database that uses a database table or view.

The Aggregate transformation aggregates and groups values in a data set.

AstAggregateOutputPathNode is a special type of output path that is used to model output paths from a Aggregate transformation in a SQL Server Integration Services dataflow task. This output path includes the calculated columns it should produce.. Connections are made by referencing an output path from an appropriate input path.

The AstAggregationDesignNode type corresponds directly to an aggregation design in SQL Server Analysis Services.

The AstAggregationNode type corresponds directly to an individual aggregation in SQL Server Analysis Services.

The AstAnalysisMetadataBaseNode class serves as an abstract base class for all SQL Server Analysis Services (SSAS) metadata that can be attached to a table object. these include both multidimensional and tabular metadata.

The SQL Server Analysis Services connection connects to a server running an Analysis Services database or to an Analysis Services project.

The Analysis Services Execute DDL task runs data definition language statements.

The Analysis Services Processing task processes Analysis Services objects such as cubes, dimensions, and mining models.

AstAttributeNode corresponds directly to a SQL Server Analysis Services dimension attribute.

AstAttributeRelationshipNode corresponds directly to a SQL Server Analysis Services dimension attribute relationship. It describes parent/child relationships between attributes.

The Audit transformation performs specified audits on the incoming dataflow rows and adds audit information to the outgoing dataflow rows.

The AstAuditOutputColumnNode type corresponds directly to an output column mapping definition in the SQL Server Integration Services dataflow audit component.

The Azure Blob Download Task provides options to download files from Microsoft Azure Blob Storage.

The Azure Blob Transfer task node is a common abstract base class for Azure Blob Upload and Download tasks.

The Azure Blob Upload Task provides options to upload files to Microsoft Azure Blob Storage.

The Azure HDInsight Create Cluster Task creates a new Microsoft Azure HDInsight cluster.

The Azure HDInsight Delete Cluster Task deletes an existing Microsoft Azure HDInsight cluster.

The Azure HDInsight Hive Task submits a Hive job to Microsoft Azure HDInsight.

The Azure HDInstight Submit Job task task node is a common abstract base class for Azure HDInsight job submission tasks.

The Azure HDInsight Pig Task submits a Pig job to Microsoft Azure HDInsight.

The Azure Storage Connection connects to a Microsoft Azure bloc storage account.

The Azure Subscription Connection connects to a Microsoft Azure subscription.

The Back Up Database task can back up one or more SQL Server databases.

The Balanced Data Distributor Transformation creates splits its input rows into equal proportions and distributes it to its output paths. This is normally used to better take advantage of the parallelism features of your target server or to distribute rows across server shards. You will need to install this component on your server as it is published by Microsoft as a download. Please see http://blogs.msdn.com/b/sqlperf/archive/2011/05/25/the-balanced-data-distributor-for-ssis.aspx for more information.

The Bulk Insert task is an efficient method of copying large amounts of data into a SQL Server table.

The AstCacheColumnNode type corresponds directly to a column that is defined in a raw or cache file format definition in SQL Server Integration Services.

The Cache connection connects to a cache.

The Cache Transform transformation writes data from a connnected data source to a specified cache. This data can later be used by the lookup transformation. Using a cache enables multiple lookups to share the same cache rather than separately loading duplicate data.

The AstCalculatedMemberNode type corresponds directly to the script definition for an MDX calculated member in SQL Server Analysis Services.

The AstCandidateKeyProfileRequestNode type corresponds directly to the candidate key data profile in the SQL Server Integration Services data profiling task, which will report which column(s) have unique values across rows and could consequently serve as keys.

The CDC Control Task provides a variety of options for CDC control operations on a CDC-enabled SQL Server database. It corresponds directly to the CDC Control Task in SSIS 2012 and higher (http://msdn.microsoft.com/en-us/library/hh758674.aspx).

The CDC Source reads data from a a CDC-enabled SQL Server table and outputs rows that reflect the changes that have taken place in the specified processing range.

The CDC Splitter component partitions rows from a CDC Source component based on its status as an inserted, updated, or deleted row.

The Character Map transformation converts character data by applying string transformation operations.

Defines a Check constraint, which can be used to enforce that data in a table or column meets specific criteria.

The Check Database Integrity task runs the DBCC CHECKDBT Transact- SQL command to verify the integrity of the database.

The AstColumnLengthDistributionProfileRequestNode type corresponds directly to the column length distribution data profile in the SQL Server Integration Services data profiling task, which will report length statistics for columns with character types.

The AstColumnNullRatioProfileRequestNode type corresponds directly to the column null ratio data profile in the SQL Server Integration Services data profiling task, which will report the frequency of null values in nullable columns.

The AstColumnPatternProfileRequestNode type corresponds directly to the column pattern data profile in the SQL Server Integration Services data profiling task, which will compute a collection of patterns that describe the values in a character-based column.

The AstColumnStatisticsProfileRequestNode type corresponds directly to the column statistics data profile in the SQL Server Integration Services data profiling task, which will report aggregation statistics for numeric and date/time columns.

The AstColumnValueDistributionRequestNode type corresponds directly to the column value distribution data profile in the SQL Server Integration Services data profiling task, which will report the number of occurences of each value for a given column.

Defines the connection referenced from the custom component.

Defines an output for a custom component.

The AstComponentScriptProjectInputBufferColumnNode type corresponds directly to a dataflow column that is mapped into an input path column of a Script Component project. This column will be exposed for reading and/or writing in the script project user code.

The AstComponentScriptProjectInputBufferNode corresponds directly to input buffer column mappings within a SQL Server Integration Services dataflow Script Component.

The AstComponentScriptProjectNode corresponds directly to the project embedded within a SQL Server Integration Services dataflow Script Component.

The AstComponentScriptProjectOutputBufferColumnNode type corresponds directly to a dataflow column that is mapped into an output path column of a Script Component project. This column will be exposed for editing to the script project user code.

The AstComponentScriptProjectOutputBufferNode corresponds directly to output buffer column mappings within a SQL Server Integration Services dataflow Script Component.

The Conditional Split transformation routes source data rows to different output paths by evaluating expressions.

AstConditionalSplitOutputPathNode is a special type of output path that is used to model output paths from a Conditional Split transformation in a SQL Server Integration Services dataflow task. This output path includes an expression that determines which rows are assigned to this path. Connections are made by referencing an output path from an appropriate input path.

The AstConfigurationValueNode type corresponds directly to an individual value setting within a SQL Server Integration Services package configuration.

AstConnectionBaseNode is the base type for all connection types that are defined in the Biml framework.

The Melissa Data Contact Verify custom component is used to detect suspicious values, standardize, normalize, verify, correct, or supplement various properties of contact information, including names, addresses, geocoding, phone numbers, and email addresses. It uses a local or remote database that is regularly updated with the latest data from the U.S. and Canada. You will need to install this component on your server as it is published by Melissa Data. Please see http://www.melissadata.com/data-quality-ssis for more information.

AstContainerTaskBaseNode is the base type that is used for all SQL Server Integration Services task containers in Biml.

AstContainerTaskNode corresponds directly to a SQL Server Integration Services sequence container task.

The Copy Column transformation copies input columns and uses them to create new columns in the transformation output.

Cube Dimension objects correspond directly to cube dimensions as defined in SQL Server Analysis Services (SSAS). They have all of the same capabilities and limitations.

A measure group associates dimensions with measures and groups measures to optimize processing. This collection is used to define a cube measure group, which references a fact table. Each fact table might be referenced by multiple cube measure groups in cases where a single fact table might be used in multiple ways. For example, a fact table that tracks customer activity might be used both in a sales and an account measure group for a sales-tracking cube.

Cube objects correspond directly to SQL Server Analysis Services (SSAS) cubes, which offer a multidimensional data storage and query mechanism.

This node defines an SSAS project (DWProj file), with associated cubes and dimensions. This object is used primarily when multiple cubes are defined within the same Biml solution and those cubes must be emitted into separate projects.

The Custom Component transformation represents a custom component in SSIS.

Defines a custom source component.

Custom tasks to run additional code or scripts during the creation of a Table, Dimension, or Fact.

SQL Server Integration Services includes several log providers that enable users to record a log of events that occur during package execution. You can also create a custom log provider.

The AstCustomConnectionNode type supports custom and third party SQL Server Integration Services connection managers.

The AstCustomTaskNode type supports custom and third party SQL Server Integration Services tasks.

The AstDatabaseFileGroupNode type provides properties to configure a group of file used to store the contents of a database on the database server.

The AstDatabaseFileNode type provides properties to configure a file used to store the contents of a database on the database server.

Database objects correspond directly to SQL Server databases, which are logical containers for tables, stored procedures, views, schemas, and other database objects. Note that databases are currently not used to genereate SQL code and can only be used to enable tables and schemas with the same unqualified name to be generated by the BIML framework.

The Data Conversion transformation converts the value in a column from its present type to a specified type and copies it to a new column.

AstDataflowColumnBaseNode is the base type for all SQL Server Integration Services dataflow task columns, including those that will original from file sources and caches.

AstDataflowColumnNode is the base type for all SQL Server Integration Services dataflow task columns.

The AstDataflowExternalColumnNode type corresponds directly to a dataflow column that describes metadata from a column defined in a remote data source in SQL Server Integration Services.

The AstDataflowOutputColumnNode type corresponds directly to a dataflow column that is mapped to a dataflow output path for passing row values in SQL Server Integration Services.

AstDataflowOutputPathNode is used to model output paths in a SQL Server Integration Services dataflow task. Connections are made by referencing an output path from an appropriate input path.

The AstDataflowPropertyNode type corresponds directly to a custom property that can be overriden with an expression on an output path or column in a dataflow task in SQL Server Integration Services.

The AstEtlRootNode type corresponds directly to a SQL Server Integration Services dataflow task.

The Data Mining Model Training destination is used to train data models in an Analysis Services cube.

The Data Mining Query transformation runs a Data Mining Extensions (DMX) querie against a specified data mining model.

The Data Mining Query task runs prediction queries based on data mining models.

AstDataProfileRequestNode is the base type for all data profiling types available in the SQL Server Integration Services data profiling task.

The Data Profiling task helps you to solve data problems by profiling specifed columns and column relationships in a data source.

The DataReader destination loads dataflow rows into an ADO.NET data reader for consumption by other applications or components.

The DB connection connects to a database.

The Derived Column transformation applies expressions to input columns to generate new column values.

AstDerivedColumnNode enables the definition of new columns in a dataflow task within a Derived Columns transformation.

AstDestinationTransformationNode is the base type that is used for all SQL Server Integration Services dataflow transformations/components in Biml that are destinations (i.e. no non-error output paths).

AstDimensionHierarchyLevelNode corresponds directly to a SQL Server Analysis Services dimension hierarchy level.

AstDimensionHierarchyNode corresponds directly to a SQL Server Analysis Services dimension hierarchy.

Dimension metadata objects include all of the information necessary to use the parent table as the basis to create a Dimension in SQL Server Analysis Services (SSAS).

AstDimensionNamedBaseNode is the base class for all attribute, relationship, hierarchy, and level elements that are bound to a dimension.

Dimension objects include all of the capabilities of regular tables and additionally correspond directly to a Dimension in SQL Server Analysis Services (SSAS).

The Dimension Processing destination loads and processes an SQL Server Analysis Services dimension.

The DQS Cleansing transformation replaces values of incoming data flow columns with corresponding values that have been corrected using rules specified in a Microsoft SQL Server Data Quality Services (DQS) instance.

The AstDrillThroughActionNode type corresponds directly to a cube drill through action that is stored on the Analysis Services cube and executed by client applications such as Microsoft Excel.

The Excel destination loads data into Microsoft Excel workbooks.

The Excel OLE DB connection connects to a Microsoft Excel data source.

The Excel source extracts data from Microsoft Excel workbooks.

The Execute Package task allows packages to run other packages as part of a workflow.

An Execute Process task can run business applications or batch files as part of a package workflow.

The Execute SQL Server Agent Job task runs SQL Server Agent jobs specified in a maintenance plan.

The Execute SQL task runs SQL statements during package execution.

The Execute T-SQL Statement task can be used to add specified Transact-SQL statements to a maintenance plan.

The Export Column transformation exports column values from rows in a data set to files.

The Expression Task will execute an SSIS expression. It is often used as a convenient host for variable assignments or to serve as a placeholder for control flow branching.

Fact table objects include all of the capabilities of regular tables and additionally correspond directly to a Measure Group in SQL Server Analysis Services (SSAS).

AstFileColumnNode is the base type for all SQL Server Integration Services dataflow task columns that originate from a source file.

The File connection can connect to existing files or folders or create files or folders if needed.

AstFileFormatNode is the base type for all flat file definition formats in the Biml framework.

The File System Task performs commands against specified files and directories.

The AstFlatFileColumnNode type corresponds directly to a column that is defined in a flat file format definition in SQL Server Integration Services.

The Flat File connection connects to a flat file.

The Flat File destination writes data to a flat text file in a format specified by a FlatFileFormat definition.

The AstFlatFileFormatNode type corresponds directly to a flat file format definition that can be consumed by a dataflow flat file source in a SQL Server Integration Services dataflow.

The Flat File Source reads data from a flat text file in a format specified by a FlatFileFormat definition.

The Foreach ADO Loop enumerates tables or table rows in data that is stored in a variable.

The Foreach ADO.NET Schema Loop enumerates specified information about the data source.

The Foreach File Loop enumerates files in a folder.

The Foreach From Variable Loop enumerates enumerable objects contained in a specified variable.

The Foreach Item Loop enumerates items in collections.

AstForEachLoopNode corresponds directly to a SQL Server Integration Services foreach loop container task.

The Foreach Nodelist Loop loops through all the nodes of an XML file that is the result of applying an Xpath expression to an XML file and enumerates and lists specified elements.

The Foreach SMO loop enumerates a SQL Server Management Objects (SMO) obect on a specified instance of SQL Server.

AstForLoopContainerTaskNode corresponds directly to a SQL Server Integration Services for loop container task.

The FTP connection connects to a File Transfer Protocol (FTP) server.

The FTP task downloads and uploads data files and directories as part of an Integration Services workflow.

The AstFunctionalDependencyProfileRequestNode type corresponds directly to the functional dependency data profile in the SQL Server Integration Services data profiling task, which will report whether all column values in one column have a 1:1 or 1:Many correspondance with a specified related column.

The Fuzzy Grouping transformation groups data set rows that contain similar values.

The Fuzzy Lookup transformation looks up values in a reference data set by using fuzzy matching. That is, matches can be close rather than exact.

The Melissa Data Fuzzy Match custom component provides a robust, highly configurable collection of options to perform fuzzy matching on any selected input data fields. You will need to install this component on your server as it is published by Melissa Data. Please see http://www.melissadata.com/data-quality-ssis for more information.

The Melissa Data Global Verify custom component is used to verify, correct, and supplement various properties of contact information across more than 240 countries, ensuring that address records are correct and complete. It uses a local or remote database that is regularly updated with the latest international data. You will need to install this component on your server as it is published by Melissa Data. Please see http://www.melissadata.com/data-quality-ssis for more information.

The History Cleanup task removes old, unneeded historical information from the database.

The HTTP connection allows a package to use HTTP to connect to a Web server to send or receive files.

The Import Column transformation loads data from files into columns in a data flow.

AstIsNullPatcherColumnNode is an abstract type that is used to define default value mappings that will replace null values in the specified dataflow column.

The Is Null Patcher will rewrite the specified columns to a default value if they have a null value.

The AstKpiNode type corresponds directly to a Key Performance Indicator (KPI) in SQL Server Analysis Services.

AstLogProviderBaseNode is the base type for all log provider types available in the SQL Server Integration Services.

The Lookup transformation combines data in input columns with data in columns in a reference data set. It is the data flow equivalent of a SQL join.

The Maintenance Cleanup task removed unneeded backup files or other maintenance-related files from the specified locations.

The Melissa Data Match Up custom component is used to identify duplicate contact records. Even when contact properties are not exact matches, the component uses fuzzy matching and a variety of scoring algorithms to identify matches. You will need to install this component on your server as it is published by Melissa Data. Please see http://www.melissadata.com/data-quality-ssis for more information.

The AstMdxFileNode type enables script definition for an MDX script commnd in a SQL Server Analysis Services cube to be imported from an external file. This provides a facility for common MDX scripts that are shared across multiple cubes to be easily managed and shared from a central location.

AstMdxScriptItemNode is the base type for all SQL Server Analysis Services script types.

The AstMdxScriptNode type corresponds directly to a cube script container in SQL Server Analysis Services. While Business Intelligence Development Studio only exposes a single script container per cube, Analysis Services permits multiple script containers to be defined.

Measure group metadata objects include all of the information necessary to use the parent table as the basis to create a Measure Group in SQL Server Analysis Services (SSAS).

AstMeasureNode corresponds directly to a measure in an Analysis Services cube measure group.

The Merge Join transformation merges data from two data sets by using a join.

The Merge transformation combines date from two sorted data sets into a single data set.

The Merge task changes a target table based on the the results of a join with a source table.

The Message Queue task can send and receive messages between SSIS packages or to an application queue processed by a custom application. The messages can contain simple text, files, or variables and values.

This is the common abstract base class for all global Biml project metadata items.

Metadata instance objects include all of the metadata specifications for a given metadata model. Note that there may be many metadata instance objects for each metadata model. The metadata model specifies the structure and rules for a collection of metadata. The metadata instance specifies the actual metadata within that model.

Metadata items specify all metadata properties, relationships, and column mappings for a given item or row within a a metadata model entity. Using a relational database analogy, if the metadata model entities were tables, metadata instance items would be the rows that populate those tables.

Metadata item entity objects are used to store actual metadata information associated with a referenced metadata model entity.

Metadata model entities specify all of the information needed to track an individual entity within the model. Using a relational database analogy, each entity would correspond to a table, while relationships correspond to foreign keys and properties and mappings correspond to table columns.

Entity relationships define the relationships that exist between the parent entity and other entities within the model. Using a relational database analogy, if the metadata model entities were tables, relationships would be foreign keys that relate those tables.

This is the abstract base class for all metadata model colmn mapping specifications.

A metadata model defines all configuration necessary for an end-user to specify and validate metadata that will be used by downstream BimlScripts to automatically generate assets.

Properties add configuration values to various objects within the metadata model.

Permitted value set objects provide a collection of permitted values to be used to constrain the allowable inputs for a metadata model property.

Filtered lookup items are used by the editor UI to provide completion lists. Each filtered lookup item will provide configuration information for a completion list. These completion lists can reference each other. For example, a column relationship may provide fields for connection, object, and column. In this case, the object lookup completion list would only contain objects in the selected connection. Similarly, the column lookup completion list would only provide columns in the selected table.

Lookup items are an abstract base class provided for backwards compatibility as additional types of filtered lookups are added in the future.

This is the class that is used as the basis for all validator rules that can be specified on a metadata model or any of its components.

The mining model receives data from the mining structure, applies a mining model algorithm, and routes the data to specified locations. Mining models can be queried directly or participate in downstream data processing.

This value displays the current cube state with respect to processing.

The MSMQ connection allows a package to connect to a message queue.

The Multicast Transformation creates multiple copies of source data and distributes them to multiple output paths.

Multiple-column table references are used to create a local column with a relationship to a multiple-column key of a regular table. Multiple-column table references can be used with foreign keys having any number of columns. Use table reference columns for a version of table references that is optimized for single column keys.

The Multiple Hash custom component is used to produce hash values for a selection of input columns using a choice of hashing algorithms. It is capable of producing multiple hashed output columns with a single instance of the component. You will need to install this component on your server as it is published on CodePlex as a community project. Please see http://ssismhash.codeplex.com for more information.

The AstMultipleHashOutputColumnNode type is used to specify an output column for the Multiple Hash component. It includes a selection of hashing algorithm and a list of references to input columns whose values should be hashed to produce hashed values for this output column.

AstMultipleInTransformationNode is the base type that is used for all SQL Server Integration Services dataflow transformations/components in Biml that have a dynamic number of input paths.

AstNamedNode is the base type for all Biml language model classes that can be referenced by name and that will be entered into the symbol table for central tracking. It provides a variety of methods and properties that are useful to the language framework.

The AstNamedSetNode type corresponds directly to the script definition for an MDX named set in SQL Server Analysis Services.

The Notify Operator task sends notification messages via e-mail, pager, or net send to SQL Server Agent operators.

The ODBC Connection specifies the settings necessary for an Open Database Connectivity (ODBC) adapter installed on the system to connect to a data source.

The ODBC Destination loads data into an ODBC-compliant database that uses a database table, a view, or an SQL command.

The ODBC Source reads a data source using one of the ODBC adapters available on the host system.

The AstOfflineSchemaColumnNode class defines the type metadata information for an individual column within an offline schema.

The AstOfflineSchemaItemNode stores all information necessary to build a package that targets a specific table or query without having to inspect the schema information for the live table or query at build time. It is essentially a cache of column type information for a table or query result set.

The AstOfflineSchemaNode stores all information necessary to build a package that targets a specific data source without having to connect to the data source at build time. It is essentially a cache of offline schema items, each containing column type information for a table or query result set.

The OLE DB command transformation executes SQL statements to access and transform external data.

The OLE DB connection connects to a datasource that requires an OLE DB provider.

The OLE DB destination loads data into an OLE DB-compliant database that uses a database table, a view, or an SQL command.

The OleDbSource reads a data source using one of the OLEDB adapters available on the host system.

The Oracle Connection specifies the settings necessary for the Attunity Oracle SSIS component to connect to a Oracle data source.

The Oracle Destination loads data into an Oracle database that uses a database table, a view, or an SQL command. This is done specifically using the Attunity Oracle Connector.

The Oracle Source reads an Oracle data source using the Attunity Oracle Connector.

The AstPackageConfigurationNode type corresponds directly to a package configuration that can apply setting information to a SQL Server Integration Services package.

The AstPackageNode type corresponds directly to a SQL Server Integration Services package.

This node defines an SSIS project, with associated project parameters and packages. This object is used primarily on projects targeted to the SSIS 2012 platform.

Defines a parameter for Data Integration Project or package.

Defines a partition function for relational partitioning

The AstPartitionNode type corresponds directly to a measure group partition in SQL Server Analysis Services.

The Partition Processing destination loads and processes a SQL Server Analysis Services partition.

Defines a scheme for mapping partitions to filegroups.

The Percentage Sample transformation generates a sample data set by randomly selecting a specified percentage of data flow rows from the input.

The Melissa Data Personator custom component is used to verify, correct, and supplement various properties of contact information, ensuring that records are correct and complete. It uses a local or remote database that is regularly updated with the latest international data. You will need to install this component on your server as it is published by Melissa Data. Please see http://www.melissadata.com/data-quality-ssis for more information.

The AstPerpectiveNode type corresponds directly to a cube perspective in SQL Server Analysis Services. Note that perspectives are only available in Developer and Enterprise editions.

The Pivot transformation creates a less normalized representation of a data set by taking multiple rows and converting them into a single with multiple columns.

Specify members for a principal node.

AstPrincipalNode defines a security principal that can be used across relational or Analysis Services databases.

The SQL Server Profiler log provider writes traces that can be viewed using SQL Server Profiler. The default file name extension for these files is .trc.

AstProjectBaseNode is an abstract type that serves as the base type for all project files (such as DTProj and DWProj) that can be defined within a Biml project.

The AstPropertyNode type corresponds directly to a property that can be overriden with an expression in a SQL Server Integration Services task.

The Raw File destination loads dataflow rows into a raw data file using a file format that is native to this component. This destination and the accompanying source component is intended to improve performance by leveraging the native file format.

The AstRawFileFormatNode type corresponds directly to a raw file format definition that can be consumed by a dataflow raw file source or a lookup cache in a SQL Server Integration Services dataflow.

The Raw File Source reads dataflow rows from a raw data file using a file format that is native to this component. This source and the accompanying destination component is intended to improve performance by leveraging the native file format.

The Rebuild Index task restores the free space on index pages.

The Recordset Destination component creates an in-memory ADO recordset that is stored in a variable.

The Reorganize Index task rearranges index pages to improve their search order.

The AstReportActionNode type corresponds directly to a cube report action that is stored on the Analysis Services cube and executed by client applications such as Microsoft Excel.

AstRetryContainerTaskNode is an abstract type that creates a for loop container that will automatically re-run all child tasks as many times as is specified.

The Row Count transformation counts rows as the data flows through it and stores the total row count in a variable after the last row is counted.

The Row Sampling transformation generates a sample data set by randomly selecting a specified number of data flow rows from the input.

Schema objects correspond directly to SQL Server schemas, which are logical containers for tables, stored procedures, views, and other database objects.

AstScopeBoundaryNode is the base type that is used for all classes that define a scope in Biml. When an object is a scope boundary, its name will appear as a component of the full scope name of any descendent objects.

The AstScriptCommandNode type corresponds directly to the script definition for an MDX script commnd in SQL Server Analysis Services.

The Script Component Destination type corresponds directly to a SQL Server Integration Services script component with an input buffer.

The Script Component Source type corresponds directly to a SQL Server Integration Services script component with output buffers.

The Script Component Transformation type corresponds directly to a SQL Server Integration Services script component with both an input buffer and output buffers.

The AstScriptProjectNode is the base class used for all SQL Server Integration Services script project types.

The AstScriptProjectSettingsNode type is used to model embedded resources that can be leveraged by SQL Server Integration Services script projects.

The AstScriptProjectSettingsNode type is used to model application settings that can be leveraged by SQL Server Integration Services script projects.

The AstScriptTaskNode type corresponds directly to a SQL Server Integration Services script task.

AstSecurableNode is the base type that is used for all classes that can accept permissions in Biml.

The Send Mail task sends messages to specified recipients about tasks, events, and outcomes of the workflow.

This node represents a server. For example, it can represent a SQL Server instance.

The Shrink Database Task, if possible, reduces the size of the specified databases.

AstSingleInTransformationNode is the base type that is used for all SQL Server Integration Services dataflow transformations/components in Biml that have a single input path.

The Slowly Changing Dimension transformation checks for dimension attribute changes in incoming data, determines how related records are updated, and specifies how the updated records are inserted into data warehouse dimension tables.

The Melissa Data Smart Mover custom component is used to identify contacts who have reloacted and automatically update their contact information. It uses a local or remote database that is regularly updated with the latest U.S. data. You will need to install this component on your server as it is published by Melissa Data. Please see http://www.melissadata.com/data-quality-ssis for more information.

The SMTP connection connects to a Simple Mail Transfer Protocol (SMTP) server.

The Sort transformation sorts input data in the specified order and then copies the sorted data to an output file.

AstSourceTransformationNode is the base type that is used for all SQL Server Integration Services dataflow transformations/components in Biml that are sources (i.e. no input paths).

The SQL Server Compact connection connects to a SQL Server Compact database.

The SQL Server Compact destination writes data to SQL Server Compact databases.

The SQL Server destination bulk loads data into SQL Server tables and views.

The SQL Server DQS connection connects to a Microsoft SQL Server Data Quality Service (DQS) instance.

The SQL Server log provider writes log entries to the sysssislog table in a SQL Server database.

The SQL Server connection connect sto a SQL Server database.

The SQL Server PDW connection connects to a Microsoft SQL Server Parallel Data Warehouse (PDW) appliance. In later versions, PDW is rebranded as the Microsoft Analytics Platform System.

The SQL Server PDW destination loads data into a Microsoft SQL Server Parallel Data Warehouse (PDW) appliance. In later versions, PDW is rebranded as the Microsoft Analytics Platform System.

The Control Flow Part enables SSIS developers to create reusable fragments of SSIS control flows. For Biml developers, this can be a useful tool for collaborating with team members that do not use Biml. Specifically, Biml can be used to autogenerate control flow parts that are consumed by manually developed SSIS packages.

AstControlFlowPartReferenceTaskNode enables the referencing and import of either an externally defined SSIS control flow part by its file path or a Biml-defined SSIS control flow part by reference.

The Package Part Base type provides an abstract base type for all SSIS package parts.

AstStagingContainerTaskNode is an abstract type that creates one or more tables at the beginning of the container, executes child tasks, and then destroys the created tables at the end of the container.

The AstStandardActionNode type corresponds directly to a cube standard action that is stored on the Analysis Services cube and executed by client applications such as Microsoft Excel.

The AstStoredProcColumnNode is used to define the input and output columns that will be exposed by the parent Stored Procedure.

AstPackageNode is an abstract type that creates an ExecuteSQL task to create a stored procedure that can be referenced elsewhere in the Biml project.

TableClone enables you to create a copy of an existing table, allowing you to add your own additional columns, indexes, and keys in order to support staging mechanisms, temp-tables, etc.

AstTableColumnBaseNode is the base type that is used for all table column types in Biml.

Columns represent regular SQL Server table columns. They have no special properties or capabilities beyond regular SQL Server columns.

This is an abstract base node for all Table and Dimension Reference column types.

Table reference columns are used to create a local column with a relationship to a key column of a table, dimension, or fact table. Table reference columns can be used only with single column foreign keys, and the column properties will be directly inferred from the key of the foreign table. Use the multiple column table reference for keys with multiple columns.

Hashed Key Columns automatically create a computed column that is an SHA-1 hash of all of the columns included in the referenced constraint. This column type is useful for creating a single column key value that mirrors a chosen multi-column key.

AstTableIdentityNode is an abstract type that represents both an identity expression and optionally a primary key on a table in a SQL Server relational database.

AstTableIndexNode corresponds directly to a SQL Server relational database index.

AstTableKeyBaseNode is the base node for all types of keys and constraints that can be defined in a SQL Server relational database.

Table objects correspond directly to regular tables in the SQL Server product. They support all of the same features and present all of the same limitations.

AstTablePrimaryKeyNode is an abstract type that represents a primary key constraint on a table in a SQL Server relational database.

AstTableSourceBaseNode is the base type for all table source definitions in Biml.

The AstTableStaticSourceNode type enables the definition of static data that will be loaded into the table on creation or when the static source is executed as a package target. If the table has an appropriate key specified, static source data can be merged into a table so that it can be changed and updated non-destructively.

AstTableUniqueKeyNode is an abstract type that represents a unique column(s) constraint on a table in a SQL Server relational database.

Tabular column objects correspond directly to SQL Server Analysis Services (SSAS) Tabular Model table columns, which offer aggregation and other options for use in analytics.

Tabular hierarchy objects correspond directly to SQL Server Analysis Services (SSAS) Tabular Model hierarchies, which organize table columns and measures into tree structures for use in analytics.

Tabular level objects correspond directly to SQL Server Analysis Services (SSAS) Tabular Model hierarchy levels , which constitute tabular hierarchies.

Tabular measure objects correspond directly to SQL Server Analysis Services (SSAS) Tabular Model measures, which allow expressions with custom logic to be provided for use in analytics.

Tabular metadata objects include all of the information necessary to use the parent table as the basis to create a table within a Tabular model in SQL Server Analysis Services (SSAS).

Tabular model objects correspond directly to SQL Server Analysis Services (SSAS) Tabular Models, which offer a tabular data storage and query mechanism.

Tabular partition objects correspond directly to SQL Server Analysis Services (SSAS) Tabular Model table partitions, which allow the data stored in tabular tables to be split among multiple chunks or partitions for better performance and management capabilities.

Tabular perspective objects correspond directly to SQL Server Analysis Services (SSAS) Tabular Model perspectives, specify permissions for models.

This node defines an SSAS project (SMProj file), with associated tabular models (also known as BI Model or BIM). This object is used primarily when multiple tabular models are defined within the same Biml solution and those tabular models must be emitted into separate projects.

Abstract base class for defining Integration Services tasks.

The Task Event Handler performs responds to events raised by tasks in the package.

AstTaskflowOutputPathNode is used to model output paths in a SQL Server Integration Services task control flow. Connections are made by referencing an output path from an appropriate task precendence constraint.

AstTaskNode is the base type that is used for all SQL Server Integration Services tasks in Biml.

The AstTaskScriptProjectNode corresponds directly to the project embedded within a SQL Server Integration Services Script Task.

The Teradata Connection specifies the settings necessary for the Attunity Teradata SSIS component to connect to a Teradata data source.

The Teradata Destination loads data into a Teradata database that uses a database table, a view, or an SQL command. This is done specifically using the Attunity Teradata Connector.

The Teradata Source reads a Teradata data source using the Attunity Teradata Connector.

The Term Extraction transformation extracts terms from input text columns and directs the terms to output text columns.

The Term Lookup transformation extracts terms from input text, places the terms in an input column, and compares these terms to terms in a reference table.

The Text log provider writes log entries in comma-separated value (CSV) format to ASCII text files with the file name extension of .log.

The Transfer Database task copies or moves a database between two instances of SQL Server.

The Transfer Error Messages task copies user-defined error messages from one instance of SQL Server to another.

The Transfer Jobs task copies SQL Server Agent jobs from one instance of SQL Server to another.

The Transfer Logins task copies logins from one instance of SQL Server to another.

The Transfer Master Stored Procedures Task copies user-define stored procedures frome one master database on to another master database on a different instance of SQL Server.

The Transfer SQL Server Objects task copies objects in a SQL Server database from on instance of SQL Server to another. The version of SQL Server being used determines what types of objects can be copied.

AstTransformationNode is the base type that is used for all SQL Server Integration Services dataflow transformations/components in Biml.

The Union All transformation combines rows from multiple input paths into a single output path, using column mappings where necessary.

The Unpivot transformation creates a more normalized representation of a data set by taking values from multiple columns in the same row and breaking it up into multiple rows with a label column and a column containing the original data value.

The Update Statistics task updates SQL Server information about data in tables and indexes. SQL Server uses the information to improve query plans.

The AstValueInclusionProfileRequestNode type corresponds directly to the value inclusion data profile in the SQL Server Integration Services data profiling task, which will report whether a proposed foreign key relationship between two tables would violate the foreign key constraint.

Defines the base class for Variables and Parameters used in Data Integration projects

The AstVariableNode type corresponds directly to a task variable in SQL Server Integration Services.

The Web Service task executes a Web service method.

The Windows Event log provider writes log entries to the application log in the Windows Event log on the local computer.

The WMI connection uses Windows Management Instrumentation (WMI) to connect to an enterprise environment.

The WMI Data Reader task uses the Windows Management Instrumentation (WMI) Query Language to run queries about a computer system.

The WMI Event Watcher task watches for and responds to Microsoft Windows Instrument (WMI) events.

The XML File log provider writes log entries to an XML file.

The XML source reads an XML data file, optionally validating it, and creates a data flow output rows with the resulting data.

The XML Task retrieves XML data, performs specified operations, and saves the updated documents to specified files or variables.