Navigation¶

• Main Page
  

• Random Page
• Create a new Page
• All Pages
• Categories
  

• Administration
• File Management
  

• Login/Logout
• Language Selection
• Your Profile
• Create Account
  

Quick Search
»
Advanced Search »

SSIS 2008

Table of Contents [Hide/Show]          Pipeline limiter          Event Log          Lookup component          Cache connection manager          Data profiling task          Change Data Capture component          Execution Location          Logging

Pipeline limiter¶

- not a component but a behind the scenes bit of code that stops high speed data coming from upstream while the slower process of writing the data out to somewhere empties the buffers. Very helpfull to see where the slow part of a data flow is if you can see where it is kicking in and for how long - use the log for this:

Event Log¶

- pipelinecomponenttime event - see how long pipeline was suspended for to limit number of in memory buffers. End component cant suck data in quick enough.

Lookup component¶

a lot faster - caching clever now. Caching options, dependent on type of work.

Cache connection manager¶

- new connection manager type, can be file or mem. Used by other components as per usual - VERY FAST.

Data profiling task¶

nice graphical UI - can dig into underlying relational data through distribution charts etc. Statistical analysis of data in rows/cols. Similar to db statistics but with extra analytics to allow data quality analysis.

Change Data Capture component¶

- used for ETL. DBs event log used to capture any rows changed since last run. Specify time window to monitor changes over.

Execution Location¶

* A package runs on the same computer as the program that launches it. Even when a program loads a package that is stored remotely on another server, the package runs on the local computer. * You can only run a package outside the development environment on a computer that has Integration Services installed. You cannot run packages outside of Business Intelligence Development Studio on a client computer that does not have Integration Services installed, and the terms of your SQL Server licensing may not permit you to install Integration Services on additional computers. SQL Server Integration Services is now a server component and is not redistributable to client computers in the same manner that the components required for SQL Server 2000 Data Transformation Services (DTS) were redistributable. To run packages from a client computer, you need to launch them in a manner that ensures that the packages run on the server.

Logging¶

SQL provider will create and use a system table in whatever db you specify in the provider setup, called dbo.sysssislog