12.1. SSIS Scalability Foundations
When it comes to identifying bottlenecks in packages, over time, you will develop that innate ability to know where to look. Similarly, you will also start designing your packages with scalability in mind, which will come out of knowing what works best for different challenges.
Some of the basics when you want to take your packages to the next level of scalability include knowing where your performance hits are, and choosing the right task to handle your data processing. When it comes to evaluating performance, the primary areas are identifying the control flow task durations and checking memory utilization. However, before diving into these areas, the first thing to look at is your SSIS service.
12.1.1. SSIS Service Status
The first thing you should check when encountering a performance problem is whether the SSIS service is started and set up to auto-start. The service provides some core functionality, such as enumerating and caching the component. By doing this, packages load faster and start up faster. The service name is SQL Server Integration Services, which uses the executable MsDTSSrvr.exe. To check the status of the SSIS service, open the SQL Server Configuration Manager and browse the SQL Server 2005 Services container, as Figure 12-1 shows.
Figure 12-1. The SQL Server 2005 Services container
The service State should be Running, and ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access