Package instantiation

If i open a package inside Visual Studio 2005, what does this action mean? In another word, does it mean that, the package gets instantiated (i.e. a package object is created ) ?

If so, the package object should resides in the memory while the package is in the open mode.

In general, the answers to your questions are yes and yes. It is not clear, though, why you ask this. Is there something you have trouble with or just trying to understand the moving parts?

Thanks,

Bob

|||

Hi,

I want to monitor SSIS packages running on system,I tried it with using RunningPackages class but it gives me running packages when I call method of RunninPackages class,

Can I monitor SSIS package execution continuously ? from where I get running package object

Thanks,

Omkar.

|||The question is related to the multiple instances in the memory. If i have opened the package inside IDE and I may want to execute the same package using other approaches such as invoked from C#.NET application or dtutil etc. Therefore each individuate application has its own package instance inside the process address space. And there should be mulitple loading for pakcage.... Please comments if this is wrong.|||

Well, it depends on what your package does. Your package may have some external dependencies that could cause contention. You will have different instances of the package object in different processes, but they still may share some resources/services.

Thanks,

Bob

OWC and AS 2005 Cube Drillthrough action

Hi There,

I setup drillthrough action on AdventureWorks sample cube, and am able
to view drillthrough through cube browser. However when I use OWC
(office web component) 11 (office 2003) to connect to the cube, I can
still open up drillthrough in the IE with all the dimension name, but
without any data.

Does OWC 11 support AS 2005 Drillthrough, we use OWC 11 on AS 2000 cube
drillthrough and work fine?

Does anyone get drillthrough working on AS 2005 cube in OWC 11?

Thanks
Dong

Hi Dong,

I haven't use plane OWC for a while and can't try this scenario right now. But if you still have a problem, please run SQL Profiler when issuing a drillthrough command and action (Discover request MDSCHEMA_ACTIONS) from OWC and Browser and see for any noticable differentces between the two. You can also post those commands in this post, may be we can find the problem together.