March 10, 2005 at 7:30 am
Hello World!
I have a box with SQLServer 6.5 (version 6.50.416) on a NT4 (sp 6a). I want to end up with a SQLServer2k (licensed for 1 processor), with a choice of OS depending on the CAL requirements (NT4 or W2k: although I have a license for W2k, I don't have any CAL's for it at the moment, nor plans to purchase - unless necessary).
I installed the SQLServer 2k (on the same machine) and searched in vain for the 'SQLServer update wizard': I don't have a menu option like 'SQLServer-Switch', and I don't have an executable called 'upgrade.exe' (which supposed to be in the backyard of the menu option).
Although I could do an BCP for the data in my production database (and regenerate the stored procedures & triggers), my concern is related to the master database: I need to preserve the logins with related passwords.
Anybody with a hint for 'what-to-do'?
Also, I need for the future to allow JDBC access to this 'future-to-be' SQLServer 2k. Does anybody knows about issues related to JDBC for SQLServer 2k on NT? I 'heard' that JDBC is supported only on W2k…
TIA,
Emanuel Ionescu
March 14, 2005 at 8:00 am
This was removed by the editor as SPAM
March 14, 2005 at 9:12 am
Hi Emanuel,
I am in the process of upgrading my last 6.5/NT4 to SQL2K/Windows 2000. I upgraded many 6.5 s and it is possible I may help you with your problems.
I did not see a case yet where Switch was not installed except for Beta 2005 Developer Edition. Swith is installed even in Personal Edition of 2000. But, again, I always select Custom install and check every line for every component during the installation.
Please, do the following: In Query Analyzer Click Query ->Results In Text and type: Select @@version. Run it and post the output here.
Also let us know what you have under Microsoft SQL Server 2000 Start Menu item
Yelena
Regards,Yelena Varsha
March 16, 2005 at 7:59 am
Thank you, I really appreciate your support!
The version, as installed, is 8.00.194. The source of all evil is the installation kit, which lacks the 'Upgrade Tools' as a sub-component of the 'Server Component' in the process of (custom) installation.
I guess I need to buy an new installation kit from MS. My legal kit is actually a Back OfficeServer 2000, but the actual installment was done from a borrowed copy.
TIA,
Emanuel
March 16, 2005 at 9:38 am
Emanuel,
A CD kit costs about $25 if you have a license for SW.
Login Transfer: Please, take a look at those articles.
I also have a script to transfer logings + SIDs, but not the passwords. This script resets password to the same as user name.
------------------------------------
Microsoft Knowledge Base Article - 331451
PRB: Copy Database Wizard Does Not Copy Server Roles When it Transfers Logins
-------------------------------------
Microsoft Knowledge Base Article - 240872
HOW TO: Resolve Permission Issues When You Move a Database Between Servers That Are Running SQL Server.
-------------------------------------
Microsoft Knowledge Base Article - 246133
INF: How To Transfer Logins and Passwords Between SQL Servers
Has a script to transfer SIDs as well.
-------------------------------------
Yelena
Regards,Yelena Varsha
March 18, 2005 at 6:41 am
Hello Yelena,
Very kind of you, I just hope that you receive same kind of responsiveness when you need it!
I have a CD with the update wizard, although the 'Update Tools' is not show as an option in the installation process. More than that, I end up with a computer running simultaneously BOTH SQLServer 6.5 AND 2000.
Books online says 'impossible', but what did they know? 🙂
But forget about installing SQL2k on a same machine with a SQL6.5
I putted a SQL2k on a brand (IBM) new machine, with a fresh installment of W2000Server (with all the service packs required). I launched the upgrade wizard (from Windows Explore) and select an appropriate export server (with 6.5).
I was told that the 'Import Server must be running SQL Server 2000'.
Which it does, and nothing else - so it's not a case of switching versions…
All I can figure to do is … to keep on doing!
Thank you,
Emanuel Ionescu
PS My source CD is the second from a BackOffice 2000 kit (bought from an authorized MS dealer)
March 18, 2005 at 10:47 am
Emanuel,
First, it is OK to run 6.5 and 2000 on the same machine. Actually, my 2-machine upgrade did not run, but the the one where I have both SQL 6.5 and SQL2000 on the same machine runs OK.
Upgrade Wizard: you start it either from the Start Menu -> Programs-> Microsoft SQL Server -Switch ->Upgrade Wizard or from the
"C:\Program Files\Microsoft SQL Server\MSSQL\Upgrade\upgrade.exe"
For the machine with 2 versions:
Make sure before you start the upgrade that it is SQL 2000 installation that is active. Your Switch menu has to have option to switch to 2000 if it currently 6.5 or switch to 6.5 if it currently 2000. Only 1 version may be active at a time.
Do you have SQL 7.0 software by chance? I don't know about installation CD from BackOffice 2000, but previously I had an installation of SQL Server 7.0 from the second CD of BackOffice 4.5 and I upgraded many databases from 6.5 to 7 on that machine and later upgraded them to 2000. Which (7.0 to 2000) is as easy as backup and restore or detach/attach.
So if something wrong with 2000 upgrade tools, try upgrading to 7.0 and then to 2000.
But first try to run upgrade on the machine that has both 6.5 and 2000 starting upgrade from SQL 2000 environment
Yelena
Regards,Yelena Varsha
March 31, 2005 at 1:56 am
Thank you Yelena!
My silence was the result of following your advice about SQLserver 7.
In the process I discovered the 'mother of all evil': I installed a named instance of SQLServer2000 instead of the 'default one'. This is the reason for not having the 'Upgrade Tools' as an option in the installation process, also for not being able to run the 'upgrade'.
Good luck to you,
Emanuel
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply