SQL 2012: Could not open global shared memory

Hello:

I imported data from one database to another using the SQL Import and Export Wizard in SQL 2012.  I copied data from tables, rather than using a SQL script/query to do so.

The wizard stated that the import was successful.  I received no errors, and everything appears to be fine.  But, in the "Validating" section, I got the warning shown in the attachment.

Is this anything to be concerned about?

Again, the instance that I was working with is SQL 2012.

Now, since I have both SQL 2012 and SQL 2008 R2 installed on this machine, it is possible that I may have gotten confused and used the SQL 2008 R2 SQL Management Studio on accident instead of the SQL 2012 SQL Management Studio to run this wizard.  Could that have caused this warning?

Thanks!

TBSupport
SQL-Server-Import-and-Export.docx
LVL 1
TBSupportAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Barry CunneyCommented:
Hi TB,
There is a MS support article describing such an issue - KB 2496375
TBSupportAuthor Commented:
Yes, but I'm on SQL 2012.
Barry CunneyCommented:
Hi TB,
Please confirm what version of windows operating system you are running on.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

TBSupportAuthor Commented:
Windows 8.
Barry CunneyCommented:
Hi TB,
By any chance do you have a Windows server that you could use to test doing the same import to see if you get similar issue.
The MS support article mentioned Windows XP, but maybe you are encountering a similar scenario.
Maybe it is an issue that potentially occurs on Windows and may not occur on Windows Server.
TBSupportAuthor Commented:
No, I'm afraid that I don't.
Barry CunneyCommented:
Hi TB,
I noticed in the warning message in the doc you attached, it mentioned 'to resolve run this package as Administrator'.
So try and run SQL Server Management Studio as Administrator and try the same import again.
To run SSMS as Administrator, right-click on SSMS when you select it from Start | Programs and choose 'Run as Administrator'
TBSupportAuthor Commented:
Hi Barry:

I saw that, too.  But, I am an administrator on my machine.  That's very odd....

TBSupport
Vitor MontalvãoMSSQL Senior EngineerCommented:
But, I am an administrator on my machine
Yes, but the Import/Export wizard might run on the behalf of SQL Server service. Just right-click on the icon and chose "Run as administrator...".

Anyway the warning is not an error. It's only saying that there's no performance counter to monitor that particular task.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.