SQL Server Integrated Service programming Basics

If you have moved data from or out of SQL Server, you can now use the data transmission service tool of Microsoft or Microsoft. DTS is an ETL Tool (abbreviated for extraction, transmission, and loading). It allows database administrators to create a series of steps to describe how data is transmitted. These "packages", just like their names, can be run in different programming languages or directly on the SQL server itself.

This idea has always been a good idea, but it is still limited in any case-if it is very convenient to use the block copy system version of an earlier version of SQL Server, it can still be honored. At SQL Server2005, Microsoft decided to turn DTS into a brand new ETL Tool-SQL Server Integrated Service (SSIS ). Migrating data from a database to another database or exporting the database in another format is the most basic use of SSIS. Here are some other reasons for using SSIS:

Data cleansing

If you have a dataset that is not "clean", for example, it is not standardized, SSIS has a series of tool sets that can be used to clean and standardize data. These include functions similar to "fuzzy" Matching and grouping, so that data that looks the same (only after different imports and exports) can be filtered out and standardized. A good example of this is that there are different types of data from different geographic regions: the same idea can be expressed in different ways, they need to be standardized before being processed.

Connect to the Analysis Service cube

You can use SSIS to directly connect data to cubes through pipelines for data mining. In addition to importing the data into the local database and then mining it, The SSIS package itself can also be used for data sources.

Integration with SQL Server Report Service

For analysis cubes, The SSIS package can also be used directly for data sources to create reports.

Complete. NET Report

This may be a hypothesis, but SSIS programming can indeed be done locally or in any. NET language through the COM object interface -- or, in fact, any language that supports COM objects.

The final result is that you import the dataset System and the package you create can work more like a converted object than static data. This idea allows users to program in advance in the form of reporting services, analysts said.

Services, data, and databases can communicate with each other. For example, archived legacy data can be used by form analysts or data mining, even if they are technically offline. Another example is data integration from Multiple Static sets. For example, in the case I mentioned above, data from multiple geographic locations.

Because SSIS is programmable, its functions can be called by the environment in a large scope. For example, an ASP. NET-driven website can be a management frontend running SSIS packages, or an independent SSIS-Connected Application that obtains and extracts data for its own use. The idea of being able to program-drive SQL Server has been around for a long time, but SSIS makes it possible to talk to all things, including things that SQL Server uses-once, in a unified manner. A programmer can also create custom SSIS extensions, such as customer data transmission or counters. You can reuse them in another application or in other environments.

The packages in SSIS can be written using Business Intelligence Design Studio, which is available with SQL Server2005. Most result files are in XML format, so they can be viewed or manually modified if needed. Note: Some functions in SSIS-Data Mining connection and fuzzy grouping and search-are available only in SQL server of the Enterprise Edition. SSIS is not available in all SQL Server 2005 Express editions. Therefore, if you create an SSIS package, you can only use it in the full version of SQL Server. Finally, when you use SSIS to create procedural solutions, they need to be designed to work in other environments that fully support SSIS.

(