Difference between revisions of "Install SQL Server"

From Heureka Wiki
Jump to navigation Jump to search
(No difference)

Revision as of 13:18, 22 December 2009

The Heureka softwares use Microsoft SQL Server 2005 for storing data (see also Introduction to Projects). The input data is stored in one database (called "forest database"), and the result data in another ("result database"). You may store data locally, on a server, or both. At an organisation with many users, it may be practical to store forest input data on a central server, and result data locally on the client machines.

SQL Server 2005 is available both as commercial versions, and as a free version. The free version is called SQL Server 2005 Express. It has a limited storage capacity of 4 GB, but apart from that it has all the functionality needed for Heureka's applications.

Installing SQL Server

  1. Installing SQL Server 2005 Express
  2. Installing SQL Server Management Studio
  3. You must have the .NET framework 2.0 or later installed (If not, th installation will automatically be invoked during installation).

Note: The file management in SQL Server is different from that one may be used to from database software such as Access. In SQL Server, there are data files, but you do not open them directly, but install them as instances in SQL Server. When you connect to a database, you will choose the name you chose in paragraph 6 above.

Install the forest database

The input database must be installed, while the result database is created programatically by RegWise and PlanWise. StandWise does save results. Instructions:

  1. Download an empty backup file (. Bak) of SLU FTP server and save to your hard disk, for example, C:\TEMP\. If you are installing on a server, the file must be available locally on the server, and you must be logged on the server. You can also use another backup of a database that already contains data, if you have access to such.

Alternative 1: Use function in PlanStart to install database

This is the easiest method which does the same as in option 2 below, but in a simpler way. You use a function in PlanStart to create a database to which you can then import forest data, for example with import a stock index. Do the following:

  1. Start PlanStart
  2. Select "Create Database Forest" from the "Tools" menu
  3. Click the "Browse"-button and select the directory where the backup file is located, eg C:\TEMP\.
  4. Select the backup file and click "Open". Note: Windows Vista may be sensitive to where the backup file is put, because SQL Server in Vista has restricted reading access. Anyhow, C:\temp\ should be OK.
  5. Enter the server name under the "Server":
  6. # If you have installed the free version, SQL Server 2005 Express, enter "localhost\SQLExpress"
  7. # If you have the commercial version of SQL Server, enter "localhost" if you install the database locally, or the server name if you are installing on a remote server.
  8. If you install locally, leave "Authentication" mode equal to "Windows authentication".
  9. In "Database name", type a database name (without blanks)
  10. Click the "Browse ..."-button next to "Location of data file", and specify a location where you want to save the database. See (4) above concerning problems with Vista.
  11. Click on "Create Database" and wait until ready.

If this does not work, then try the options below. See end of this page for common problems.

Alternative 2: Run the "Restore" in SQL Server Management Studio

  1. Open Management Studio. Enter the server name (localhost, localhost\SQLExpress, or the server name).
  2. Right click on "Databases", select "New Database ..." and enter a name for the new database (no blanks or spaces)
  3. Right-click the new database, select "Tasks" > "Restore" > "Database ...".
  4. As the source, select "From device" and "..."-button. Click "Add", and locate the backup-file.
  5. Check "Restore" for both files (including log-file if it exists)
  6. In "Options", select "Overwrite ..." and change the "Restore as ..." to valid paths (folders must exist on your computer if you install locally, and on the server if you install on a remote server.

Alternative. 3: Installing an .mdf file via the "Attach"-option in SQL Server Management Studio

This alternative is available if you have an -mdf-file instead of a backup (.bak) file.

  1. Open Management Studio. Enter the server name (localhost, localhost\SQLExpress, or the server name).
  2. Right click on "Databases", select "New Database ..." and enter a name for the new database (no blanks or spaces)
  3. Right click on "Databases" and select "Attach".
  4. Click "Add" and select the .ndf file.
  5. In the "Database details', check and if necessary edit the file path to valid ones.


Known issues

  • If you experience problems such as "Cannot connect ..." it may be due to that the local database server is not started. Go to Control Panel > Administrative Tools > Services. Make sure "SQL Server (SQLExpress)" or "SQL Server (MSSQLSERVER)" is running. If not, right click and select "Start". Make sure it is set to start automatically.
  • If you experience problems such as error 1069 and the server does not seem to be running, it may be because you have changed your Windows or AD password. The SQL Server service must be updated manually, it is not done automatically. Under Administrative Tools > Services, right-click SQL Server (MSSQLSERVER) or SQL Server (SQLEXPRESS) and select "Properties", tab "Log on", and enter the password.
  • Vista user? When running SQL Server 2005 Express in Vista environment it may be necessary to edit permissions [1]. Try the following:
  1. Log in to SQL Server 2005 Express as an administrator by right-clicking the SQL Server Management Studio and select "Run as admininstrator" (possibly you may have to go into the "Control Panel" , select "User" (?) and disable the UAC).
  2. Select localhost\SQLExpress as the server.
  3. Select the "Security" option from the tree view in Object Explorer.
  4. Right click on the "Login", select "New Login". Add User, type AD\nnn.
  5. Before you close the window for "New login", click "Server Roles" and select "Sysadmin".