Just go the the setup program on the CDROM and follow the steps. I chose 'custom' install because I wanted to get as much documentation on my hard disk as possible. I also elected to intall as many Active X/MDAC/ADO/ADODB components as possible. I don't know whether or not I needed all this stuff. I doubt it some how.

To restore the database just go to Enterprise Manager (under the 'M$ SQL Server' part of the start menu). Create a blank database called 'ceetak' and then go 'Actions'->Restore Database. Choose 'From Filegroups or Files' in the radio buttons in the middle of the dialog. It should say that it is restoring to the database 'ceetak'.

This backup should restore absolutely everything. See other question about connecing to this database via ODBC.

-- Anonymous, February 11, 2002

Answers

Notes:

1.To use the 'Filegroups or Files' option for a new database, you will have to create a backup first of the new (empty) ceetak database

2.Alternatively, use the Disk option to navigate to the required file - after copying it from the CD to your hard disk (read only devices are not presented as backup source devices)

3.After restoring, you must refresh the views of the tables and stored procs etc in order to see them. This is a nasty bug - it will show the old, pre restore tables/procs unless you do so, making you feel as if teh restore failed!

-- Anonymous, February 13, 2002

Note that although the database is restored from backup with user Ao98X6 it is probably simpler to delete this user and create a new login at the parent database level (look in folder 'security') with Ao98X6/AaCKP01. Then give this login access to ceetak, and make its default database ceetak. The user in the database is created as part of the creation of the login - by far the most sensible approach, unfortunately not the one that Sybase adopted.

-- Anonymous, February 19, 2002

There is another gotcha wrt setting up the login. You should set up the Ao98X6/AaCKP01 user to have role database owner in ceetak. This is acheived by going to Database Access in the SQL Server Login properties dialog (under the 'Security' folder at the level of the main server (called 'CENTREX' on my PC, after the hostname).

Another thing, the CD-Key to install SQL Server is H6TWQ TQQM8 HXJYG D69F7 R84VM.

When you set up the ODBC connection there is no need to specify the login and password to be the wacky Computer Core Ao98X6/AaCKP01 combo - sa will do, and probably anything else.

-- Anonymous, February 20, 2002

I encountered a terrible problem when I installed SQL Server 2000 on my ME machine. After I rebooted the machine would not allow any incoming or outgoing connections on TCP-IP.

I 'fixed' this in the Server Network Utility by specifying that I wanted to use another protocol than TCP-IP. Unfortunately I chose named pipes, which is not supported on Win9X operating systems! (No, it didn't detect that, or if it did, it omitted to mention it to me.)

Anyhow, after re-booting again and reverting to TCP-IP, on the basis that use of the server/web site was more important than talking to the outside world, I discovered myself again in a position that the server was working and the TCP-IP networking was working again, as it was before I rebooted. I will proceed with caution.

Presumably my option to get these things together is to let the server talk IPX/SPX (netBEUI is not an option) to clients, leaving TCP-IP for regular http, filesystem access etc. There must be a way around this. Watch this space for further discoveries.

-- Anonymous, February 20, 2002