Diary of a SQL Server 6.0 to 6.5 conversion: Rob Kraft - Empower Trainers & Consultants, Inc. 10/24/96

On monday I ran chkupg65.exe against both of the SQL Servers to be upgraded.
The highest status number returned was 8 for some databases that had keyword conflicts for column names
such as SIZE, ACTION, WORK, TIME, DATE, MONTH, and YEAR.
No action was taken to change these column names. All reports said (no problem).

On wednesday morning I backed up all test databases.

On thursday morning I backed up the critical application databases as well as master and msdb.
Then I stopped SQL Server and SQLExecutive on SQLServer1(the first SQL Server).
Then I backed up the StudentDB application .dat file(to an NT Server named NTServer1) and the master
and msdb .dat files(to an NT Server named NT_SERVER2\c$) using File manager.
6:06 Ran upgrade to 6.5 on SQLServer1
error during upgrade - could not open SQLMGR.exe - I clicked on retry and it continued okay
(later realized I had the 6.0 version of SQLMGR.exe open)
6:12 error log of upgrade listed 7 stored procs that it could not upgrade:
2 test procs, sprptBillingByClass in Training db, vrptClass in Testing db,
sp_GetSubSites in SMS, sp_GetSubGroupSites in SMS, and same two in smstest
(no action taken for these procs. we don't use them)
6:27 error log records sql shutdown.
6:29 Started SQL Server on SQLServer1


6:05 stopped sql server and sqlexec on the second SQL Server(IIS_Server)
6:23 backed up master and msdb dat files(to an NT Server named NT_SERVER2)
6:47 Ran upgrade to 6.5 on IIS_Server
(from error log)
it booted to single-user mode
msg - sql server shut down by request - error 17966, severity 18, state 0
it apparently restarted self
6:54 couldnt upgrade spcert_idsandexams in certification db
(no action taken for this proc.)
7:05 message - running low on virtual memory. 'Close some apps then go to control panel system and
create additional paging file.' I just closed control panel and explorer and said ok.
(page file was at 20mb)
7:12 this version of log says it shutdown sql server
setup is still running
message - disk is full at 91% complete. I deleted some files and told it to continue.
message - disk is full at 92% complete. I deleted more files(msquery, msinfo, and a lot of system help files)
it continued to 100%
7:50 I used ctl-atl-del to end the setup task - it seemed to be hung since 7:12
7:52 server restarted - single user mode
I removed the single user mode flag and two ttrace flags T363 and T4022
7:56 I shutdown server and restarted it. all seemed well.

8:30 Sam and Bill could not run our StudentDB application on SQLServer1(application error)3265.
8:30-9:30 I found machine with Visual Basic, installed Visual SourceSafe, loaded StudentDB code
10:00 Found that system stored procedure sp_helpuser had been changed in version 6.5 and returns a column named
GroupName instead of Group_Name(which is what our program looks for).(We should have tested better!)
(I modified the system stored proc as a quick fix: changed returned column GroupName to Group_Name)

11:04 failed to start SQLExec on IIS_Server - invalid pwd
I added password(don't know why it was lost) using Control Panel - Services
11:44 still failed to start SQLEXEC on IIS_Server - error 109
1:22 SQL EXEc failed to start on SQLServer1 as well - had to add password
1:28 changed following registy entry on IIS_Server which probably was not updated
because I had cancelled SQL Setup before it was complete:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLSERVER\MSSQLSERVER\CurrentVersion to 6.50.201
This resolved error 109.