Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

SSIS package could not open global shared memory to communicate with performance DLL

Tags:

package

ssis

I am working on a .dtsx file that reads from a database and outputs a flat file. While testing the package, using SQL's Execute Package Utility, I got this 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's console.

In my research I got mixed messages as to how to deal with this. One person said it is an issue with data types between the source and data conversion. Another said it was merely a warning that can be ignored as long as you don't need performance counters (which I don't believe I do). I also found where it is an issue on computers running xp with no SQL Service packs, but I am on Windows 7.

Should I be concerned with this warning?

like image 877
Ben Avatar asked Jun 27 '12 13:06

Ben


3 Answers

If you want to prevent this warning from occurring, you can add the user account used to execute the package (e.g. your account and/or the SQL Server Agent account) into the local group "Performance Monitor Users".

If this change is made for any services e.g. SQL Server Agent, the service will need to be restarted for the change to take effect.

like image 98
Nathan Griffiths Avatar answered Nov 18 '22 06:11

Nathan Griffiths


My understanding is that is UAC not allowing VS/BIDS access to the performance counters. For day-to-day package execution, you are fine. It is not impacting the ability of SSIS to run nor does it alter the outcome of data transformations.

like image 37
billinkc Avatar answered Nov 18 '22 06:11

billinkc


The @Nathan fix didn't work for me

What sorted it was running Visual Studio as administrator ... even though my account is in Local Administrators group

like image 2
SteveC Avatar answered Nov 18 '22 05:11

SteveC