Destination components have one or more inputs and zero outputs.At design time, they create and configure connections and read column metadata from the external data source.During execution, they connect to their external data source and add rows that are received from the components upstream in the data flow to the external data source.If the external data source exists prior to execution of the component, the destination component must also ensure that the data types of the columns that the component receives match the data types of the columns at the external data source.This allows for multiple conditions to be checked in one location.CHECK constraints are similar to FOREIGN KEY constraints in that they control the values that are put in a column.
Custom destination components are useful when you need to connect to data sources that cannot be accessed by using one of the existing source components included with Integration Services.
There are a number of different processes that can be used to make sure your data validates against your business rules.
Data validate rules can be enforced within your application code in the application layer; or data can be validated by the database engine.
datatype, define precision and scale instead of width. You can also invoke transparent data encryption to encrypt data before storing it in the datafile.
A row is a collection of column information corresponding to a single record. Then, if users attempt to circumvent the database access control mechanisms by looking inside datafiles directly with operating system tools, encryption prevents these users from viewing sensitive data.