If you are not using a SQL*Server Database, then you must do the Oracle Database Setup or go back to Installation Table of Contents.
If you have not installed Microsoft SQL*Server, you will need to do that first. See the installation documentation included with SQL*Server.
**It's always a good idea to save the output logs when running any script -- they may come in handy should a problem occur.
* Beginning with Unanet 3.3, we no longer support SQL Server 6.5. On the Properties / Option tab of your database, make sure the Compatibility Level is set to at least "Database compatibility level 70".
These instructions may vary slightly depending on whether you are using SQL Server 7 or 2000.
Open your Microsoft SQL Server Enterprise Manager. If you're new to this product, this can be found in Start\Programs
You should see the Console Root at the top of the structure followed by Microsoft SQL Servers and SQL 7.0 Machines (SQL Server Groups). If you have not made a connection to your new setup, you can do so by right clicking SQL 7.0 Machines (SQL Server Groups) and registering the new server. Once this is completed, and you have made the connection to your server, indicated by the red "lightning bolt", click on the plus sign, expanding the server's components. You will see five folders expand within this. Click on the plus sign to expand the folder "Databases" to see what the contents are. Right click on Databases and chose New Database. A popup dialog box will appear with the cursor flashing in the name section enter for ease of installation, enter the word unanet. (If this is what you would like to call it.)
These instructions assume you have created the database and called it unanet as explained in the Create Database section above. The database scripts are located in the Unanet Home Directory in a directory called database\sqlserver. The default location of the scripts is: C:\Unanet\database\sqlserver.
Note: If the database was named something other than unanet, you will need to edit the sqlpermissions.sql script, substituting the new database name prior to executing that script.
From SQL Enterprise Manager, go to the Tools menu, and select SQL Server Query Analyzer.
In the DB drop down of the SQL Server Query Analyzer, make sure the unanet database is selected. Double check that the database you are about to run this against is the unanet database (should be displayed in the drop down list box). If not, then change to the unanet database. This is very important. We don't want to run these scripts in any other database.
Once you are sure we are using the unanet database, open folder icon located in the upper left hand corner of the Query window. Go to the directory that has the Unanet SQL database scripts (C:\Unanet\database\sqlserver) and open the file sqlunanet.sql. Press the green arrow (the "Play" button) and wait for the script to finish. You will know it is finished when the red square ( the "Stop" button) turns off, and the green arrow comes back. It may take a few minutes. When the script is finished you can scroll down the results window and make sure there were no errors during execution.
Next we need to run the permissions script. Go to the open icon again, and it should already be in the folder you were at, which should be where the sqlpermissions.sql. are residing. Select the file sqlpermissions.sql. Press the green arrow and wait for the script to finish. (wait for the green arrow to come back on).
That's it for running the two SQL Scripts. Close the SQL Server Query Analyzer and return to the SQL*Server Manager. Close the Microsoft SQL Server Enterprise Manager application.
If you are experiencing the "Database is not currently available" error, you might check out the following common configuration issues.
Once the database is setup it is time to connect the web server to the Unanet Database.
Back to Installation Table of Contents
Copyright © 1998-2002 Computer
Strategies, Inc., All Rights Reserved.
Last revised: September 13, 2002.