March 8, 2006 at 3:07 pm
In preparation for upgrading to SQL Server 2005, I run the Upgrade Advisor and it gave me the warning:
Existing Meta Data Services packages should be moved to SQL Server storage (in the msdb database) or to structured storage files before you upgrade. SQL Server 2005 does not install support for SQL Server 2000 Meta Data Services; therefore the Package Migration Wizard will be unable to access Meta Data Services packages after upgrade in the absence of the SQL Server 2000 Client Tools.
I look under the DTS>Meta Data Services Packages node and there are no objects. Is there somewhere else I need to look and how do I move the packages to SQL Server storage? Or can I ignore this warning?
March 13, 2006 at 8:00 am
This was removed by the editor as SPAM
November 2, 2006 at 2:26 pm
I am having the same problem, I've deleted all the DTS package and have rerun the MSSQL 2k5 Upgrade Advisor and still get the meta data service pre-upgrade issue as posted . Please help!
February 9, 2007 at 3:54 pm
Same issue~~~~~~ Can anyone help point me in the right direction?
November 2, 2007 at 8:11 am
I'm sure this is too late for the poster, but I found this info on Google:
You can open the package by going into Enterprise Manager, Open the server node (usually (LOCAL)) then go to the Data Transformation Services, and then to the Meta Data Services Packages node, open each package and then from the Package menu, click save as, then tell it to store to a SQL Server (will save it in the MSDB database) or Structured File Storage to save it to a file.
Hope it helps.
April 28, 2012 at 12:10 am
It helped me a lot after 5 years!
Now, I checked what I had in "Data Transformation Services" >> "Meta Data Services Packages"
I removed all the objects there, since they were testee ones. Now there are no objects there, but I still get a warning from the upgrde advisor which says "Existing Meta Data Services Packages should be moved to SQL Server storage (in the msdb database) ..."
And it names them (the removed packages) in a list which says "Upgrade advisor may be unable to scan a package ..." {Although they are already removed)
Can anyone help?
June 26, 2016 at 6:23 am
Another 4-years after previous post (on 2012)! it also helped me evaluate the case. I have the same problem (no packages, but the warning exists)
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply