SQL SERVER 4.2 MANUAL INSTALLATION 11-17-92 4.2 manual installation is currently required for customers running OS/2 2.0 with a boot partition other than drive C:. 4.2 manual installation is also currently required on Windows NT, including the October Beta version of Windows NT. There are updated Windows NT OS/2 subsystem DLLs that will allow 4.2 to install successfully on the October beta version of NT. These are available from MS Product Support Services. Before starting verify the following items: (1) Check that the disk partition on which OS/2 swap file SWAPPER.DAT or Windows NT PAGEFILE.SYS resides has at least 10MB free space. The location of SWAPPER.DAT can be found in CONFIG.SYS, on the line starting with "SWAPPATH". On Windows NT, you can search for the filename PAGEFILE.SYS, or check the Windows Control Panel "System" applet. (2) Verify SQL Server is not running by doing a "PSTAT /c | MORE" from the OS/2 prompt. The Windows 32 SDK has an equivalent utility, PSTAT.EXE. (3) Verify no SQL Server or DBLIB program is running on the SQL Server machine. This includes SAF, ISQL, Q+E, etc. You may want to use the OS/2 file manager or equivalent to search all disk partitions for the files PDBLIB.DLL and DBNMPP.DLL. On Windows NT, just use the DIR /S command. No older versions of these files should be present on the machine. Then begin the manual installation: Comments: (a) Drive d:\ is used the following example. (b) Capitalization used for clarity only. DOS, OS/2, and Windows NT are not case-sensitive. Note: In the following example the SQL Server version 1.X strict compatibility code page and sort order are installed. You may select a different code page and sort order if you do not require compatibility with version 1.X. In this case just change the names CP850 and NOCASE34.850, below, to the desired code page and sort order. (1) Create necessary directories. (a) md d:\sql (make the \sql directory) (b) md d:\sql\data (make the \sql\data subdirectory) (c) md d:\sql\binp (make \sql\binp subdirectory) (d) md d:\sql\dll (make \sql\dll subdirectory) (e) md d:\sql\charsets (make \sql\charsets directory) (f) md d:\sql\charsets\cp850 (make \sql\charsets\cp850 directory) (g) md d:\sql\install (make \sql\install directory) (2) Unpack files. Execute the UNPACK program from the A: drive. (a) copy unpack.exe program from the SQL Server OS/2 Setup Disk to someplace on your local hard drive that is on the searchpath. (b) unpack sqlservr.ex@ d:\sql\binp\sqlservr.exe (executed from the A: drive) (c) unpack instmstr.sq@ d:\sql\install\instmstr.sql (d) insert the SQL Server OS/2 Disk 2 (e) unpack bldmastr.ex@ d:\sql\binp\bldmastr.exe (f) unpack isql.ex@ d:\sql\binp\isql.exe (g) unpack charset.ex@ d:\sql\binp\charset.exe (h) unpack nocase34.85@ d:\sql\charsets\cp850\nocase34.850 (i) unpack pdblib.dl@ d:\sql\dll\pdblib.dll (j) unpack dbnmpp.dl@ d:\sql\dll\dbnmpp.dll (k) unpack instcat.sq@ d:\sql\install\instcat.sql (l) unpack instmodl.sq@ d:\sql\install\instmodl.sql (m) unpack helpsql.sq@ d:\sql\install\helpsql.sql (5) Edit the CONFIG.SYS file of the machine and add d:\sql\dll to the LIBPATH setting, and d:\sql\binp to the PATH setting. Shutdown and reboot the machine. (6) Create MASTER database. bldmastr /dd:\sql\data\master.dat /c /s 7680 (7) Start SQL Server (preferably with the following syntax) SQLSERVR (executed from the \sql\data directory) You will see the SQL Server errorlog begin scrolling past the screen as SQL Server starts. It will not return to a command prompt, but continue displaying the errorlog screen. This is normal. (8) Switch to another screen OS/2 screen group and run the CHARSET program with the following syntax: CHARSET -P -Ld:\sql\charsets\cp850 nocase34.850 The CHARSET program will acknowledge its successful completion. Note: It is not mandatory to create the \sql\charsets\cp850 directory, and copy the NOCASE34.850 file there. You could optionally place the file elsewhere, (even on a different drive letter) and use a different syntax to invoke the CHARSET program. Here is an example of this: (a) MD d:\tempdir (b) Copy NOCASE34.850 d:\tempdir (c) CHARSET -P -Ld:\tempdir nocase34.850 (9) Using ISQL, Log into SQL Server and run the following query: (See 4.2 Language Reference, page 482, for details on how to run ISQL.) Below command syntax is case-sensitive. update sysconfigures set value=49 where config=123 In the above example, the value 49 represents the 'strict compatibility' sort order. If you loaded another chacter set, you should use the corresponding sort ID for that character set. Following is a list of character set/sort order files, and their corresponding sort ID: Charset/Sort file ID altdict.850 55 altnoacc.850 57 altnocs.850 61 altnocsp.850 56 cp850bin.850 40 diction.850 41 noaccent.850 44 nocase.850 42 nocase34.850 49 nocasepr.850 43 diction.iso 51 iso_1bin.iso 50 noaccent.iso 54 nocase.iso 52 nocasepr.iso 53 cp437bin.437 30 diction.437 31 noaccent.437 34 nocase.437 32 nocasepr.437 33 (10) Then run this query: reconfigure with override (11) Use the SHUTDOWN command to shut down the server. (12) Start SQL Server (preferably with the following syntax) SQLSERVR (executed from the \sql\data directory) SQL Server should indicate that the Default Sort Order has been successfully changed, and that SQL Server is shutting down after verifying System Indexes. (13) Start SQL Server (preferably with the following syntax) SQLSERVR (executed from the \sql\data directory) (14) Run the following scripts in the indicated order to complete 4.2 installation: INSTMSTR.SQL INSTCAT.SQL INSTMODL.SQL HELPSQL.SQL And optionally: INSTPUBS.SQL ADMIN2.SQL Typical script running times on 386/33: INSTMSTR.SQL 7 min. INSTCAT.SQL 1 min. INSTMODL.SQL 1 min. HELPSQL.SQL 3 min. INSTPUBS.SQL 2 min. ADMIN2.SQL 2 min. Example of how to run a script on the server machine with ISQL: isql /Usa /P /iINSTMSTR.SQL > INSTMSTR.OUT This should complete a manual installation of a 4.2 SQL Server.