The migration performance of SSIS and Oracle for SQL 2005

Having been concerned about SSIS performance issues with SQL Server 2005, one of my fellow testers tested it for reference.

There is a part of the project data migration work, frankly, from the old system to switch data in the new system model, the old system data sources are more complex and diverse, the new nature is Oracle9.2.

This is a one-time job, with SQL naturally is the fastest way, whether it is the speed of development or data transfer. But party a must see the interface, hope this is a molding tool, no way, party A is God.

The company originally also has a migration tool, but can only apply to the table on the table of the switch, complex some powerless, and the data is very slow, used by people are to it without language.

New development, not to mention the cost and effect, light time is not good. No way, had to look at the current popular ETL tools.

There is no doubt that the forefront of the market, certainly Informatia and DataStage.

Informatia did not, had to see whether DataStage can adapt to the current functional requirements. Do not want, although it is a graphical interface, it is not easy to use, and after installation, Windows can not be separated from the domain environment, and not the server version of Windows can not run Paralle Job. Depressed.

After two days of trial, put down temporarily. Microsoft's ease of use is more appealing to me than its powerful features. Try SSIS in SQL Server 2005, known as Enterprise-class ETL.

After a use, did not want to really a bit like it, from the introduction and the interface to look at a little less than datastage function, performance, HA, the following is what I have to say.

The slowest part of the ETL tool is the L part, which, according to the general statement, can account for four-fifths of the total time, so this is the key.

The test is not complex, is the same data extraction, transformation, and then loaded with a different drive to run it separately, the destination library has been identified as Oracle, so there is no room for much.

In SSIS, there are two drivers that can connect to Oracle databases, one is Microsoft OLE DB Provider for Oracle and the other is Oracle Provider for OLE DB

Accidents do not know, really long a lot of insight.