Geek asks and answers

SSIS package could not open global shared memory for communication with DLL performance

I am working on a .dtsx file that reads from a database and outputs a flat file. When testing the package using the SQL query execution utility, I received the following warning:

Warning: Could not open global shared memory to communicate 
  with performance DLL; 
  data flow performance counters are not available.  
  To resolve, run this package as an administrator, 
  or on the system console.

In my research, I received mixed messages on how to deal with this. One person said that this is a problem with the data types between the source and the data transformation. Another said that it was just a warning that can be ignored if you do not need performance counters (and I do not believe that they are needed). I also found where this is a problem on XP computers without SQL service packs, but I'm on Windows 7.

Should I be concerned about this warning?

+7
source share
4 answers

I understand that UAC does not allow VS / BIDS access to performance counters. For the daily execution of the package, you are fine. This does not affect the ability of SSIS to work and does not alter the result of data transformations.

+7
source

If you want to prevent this warning, you can add the user account used to execute the package (for example, your account and / or SQL Server agent account) to the local group "Performance Monitor Users".

If this change is made for any services, for example. SQL Server Agent, the service must be restarted for the change to take effect.

+13
source

@Nathan

, Visual Studio ...

0

The "local administrators" group allows you to work with administrator rights with a separate request, for example, "run as administrator". This does not mean that you run with administrator privileges all the time.

0
source

More articles:


All Articles