Eric,

I have been running a Database on the SQL 2000 beta version for some time now and we are close to hitting the wall for the eval period to end. We purchased the release version of SQL 2000 but when I go to install it will not upgrade the Beta version to the release version. I run through the install wizard and when it gets to the point asking what install you want the upgrade portion is grayed out. I did install a new instance of SQL 2000 but from what I can see I am able to move or copy the data files from B2 to the release version but cannot copy or move the DTS packages (over 50) that I have created. I have over 14gb of data sitting in this B2 version and am now very shell shocked at what I am seeing as an inability to upgrade as I was told by several Microsoft tech types here in Minneapolis. Any help you can provide would be appreciated.

Jim K.

-- Anonymous, March 01, 2001

Answers

Jim,

I don't find any mention of upgrade problems on the usenet forums.

I suggest you call Microsoft's PSS (Product Support Services) team. These are people who support all MS's products, write fixes, take the calls, sort out workarounds etc. They work 24x7x365. You can call them by phone. (1-800-936-3500 in the US.)

For details of your nearest PSS support center and other info try: http://support.microsoft.com/support/supportnet/default.asp http://www.microsoft.com/support/customer/itpro.htm

To report on the Web :- http://www.microsoft.com/technet/support/incident.asp http://support.microsoft.com/support/webresponse.asp

All incidents are chargeable either to your credit card or an existing account. The charge WILL be reimbursed if the problem turns out to be a Microsoft bug, or a feature that hasn't been publicly documented. The person answering the phone cannot know it's a bug, so they have to take details of your credit card before passing you on to a technician. When the call is closed the technician decides whether to mark the call as "free" in which case you get a refund automatically. I have often had a discussion with the technician before ringing off to persuade him or her that the problem was indeed a bug or undocumented feature. (Same for Web incidents.)

Good Luck,

Eric

-- Anonymous, March 02, 2001