Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Configure memory for Integration Services service and monitor current use of memory by SSIS Expand / Collapse
Author
Message
Posted Thursday, December 18, 2008 8:46 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 2:42 PM
Points: 1,851, Visits: 3,575
Apologies if this has been asked before, but I have the following 2 questions:

(1) How can I find out how much memory is being "used" by the SSIS service?
(2) How can I configure the max memory available to the SSIS service?

Thanks!


__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #622180
Posted Friday, December 19, 2008 9:40 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 7:04 PM
Points: 1,114, Visits: 2,192
This is unusual question, Marios. Why would you want to know how much memory is consumed by the SSIS service? Do you have an issue in particular?

I don't think you can control SSIS service maximum memory.


---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Post #623136
Posted Friday, December 19, 2008 10:17 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 2:42 PM
Points: 1,851, Visits: 3,575
CozyRoc (12/19/2008)
This is unusual question, Marios. Why would you want to know how much memory is consumed by the SSIS service? Do you have an issue in particular?

I don't think you can control SSIS service maximum memory.


The reason is that I have a server (32-bit OS) with 8 GB of RAM, hosting 2 db-engine instances and the SSIS service.

I have enabled AWE for one of the instances, setting max memory to 4 GB.
The other db-engine instance can access the default maxmemory of 3 GB (3-gb switch is enabled).
The SSIS service process can access up to the default of 2 GB (not sure if the 3-gb switch affects it as well).

I would like to limit the SSIS service to a max memory of 1 GB, if possible, to avoid memory contention among the 3 processes. But, first I want to monitor memory usage by the SSIS service, to ensure I don't starve it of needed resources.

SSAS gives one the ability to configure min/max memory, why isn't SSIS?



__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #623171
Posted Friday, December 19, 2008 10:45 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 7:04 PM
Points: 1,114, Visits: 2,192
There is no place where you specify global limit for SSIS processes. You control memory consumption granulary, by controlling specific SSIS tasks memory constraints. A good example is the Lookup transformation where you can limit the amount of memory in use for caching. The SSIS data flow task processes data in chunks, so if you don't use large buffers you will not have problems. I think you have to be more concerned about CPU contention. SSIS can be quite CPU intensive.

p.s.

I'm wondering why you are not using 64bit OS if you have 8GB of memory?


---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Post #623194
Posted Friday, December 19, 2008 10:50 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 2:42 PM
Points: 1,851, Visits: 3,575
CozyRoc (12/19/2008)
There is no place where you specify global limit for SSIS processes. You control memory consumption granulary, by controlling specific SSIS tasks memory constraints. A good example is the Lookup transformation where you can limit the amount of memory in use for caching. The SSIS data flow task processes data in chunks, so if you don't use large buffers you will not have problems. I think you have to be more concerned about CPU contention. SSIS can be quite CPU intensive.

p.s.

I'm wondering why you are not using 64bit OS if you have 8GB of memory?


We are thinking of moving to 64-bit, and it can't be soon enough. :)

I guess then SSIS is limited by the default 2 GB of virtual memory available to processes in 32-bit OS?

I wonder why MS did not think of providing an API for configuring memory at the global level, just as can be done in the db-engine and SSAS instances... It seems like a serious omission to me.



__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #623195
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse