Mounting a database on SQL Server

We will show you the user setup of the database clamping on SQL Server in the following steps.

1. Transferring and distributing the database from an FTP server

The user opens ftp.datalab.si/databases/ via File Explorer or any internet browser.

By clicking on the relevant database from the list below, you can download the different databases.

The user usually downloads the file to the Downloads/Downloads folder (computer setting).

After downloading the database from the FTP server, it must be extended from the archive using an appropriate extender.

WARNING For fast archive file expansion, we recommend the free 7zip.

The downloaded and extended backup of the (extension .bak) database from the archive is saved by the user to the location that was specified as the backup when SQL Server was installed - the backup folder.

In our example, the user selects the file C:\#sql\backup.

HINT See the link to install SQL Server - Database Engine Configuration step.

2. Restoring (clamping) the database to the SQL server via Management Studio

The user searches for Management Studio in the Start menu and launches it. Once the program starts, it logs on to the SQL Server.

WARNING To install, start and log in to SQL Server via Microsoft SQL Management Studio, please see Downloading and installing Microsoft Management Studio.

After logging in to the SQL server, in Object Explorer the user extends the instance (usually .\DATALAB) by clicking on plus.

Highlight the Databases section by right-clicking and selecting the Restore Database menu.

A new Restore Database dialog will open.

In the menu under Source, select the Device radio button, then select ... to open a new Select backup devices dialog.

By clicking on the Add button, it finds the database that was previously downloaded from the FTP server and extends it with the appropriate extender.

The user searches for the extended database on the hard disk (usually called SI_XX.bak), selects it and confirms his/her choice by clicking on the OK button.

After selecting the database, in the Select backup devices window, the rebel confirms by clicking the OK button.

The Restore Database p dialog box prompts the user to arbitrarily name his database on the SQL Server under the Destination section in the Database field.

We name a regular database with the short name of the company for which the new database is clamped.

Once you have named your database, you can confirm that it is mounted on your SQL Server by clicking the OK button in the Restore Database dialog.

WARNING Management Studio will install the database in the location we specified when installing SQL Server (data, log). For more details, see Download and install. In case you want to change the location of the restored (.mdf and .ldf) files, you can change the location in the Select a page | Files section. The database can also be plugged in manually, via the SQL editor with the command: RESTORE DATABASE[SI_MF] FROM DISK = N'C:\#sql\backup\SI_MF.bak' WITH FILEWITH FILE MOVE N'DataLab_Data' TO N'C:\#sql\data\MOJA_PRVA_BASE.mdf', MOVE N'DataLab_Log' TO N'C:\#sql\log\MOJA_PRVA_BASE_1.ldf', NOUNLOAD, STATS = 5 GO

If our database has been successfully connected to the SQL Server, we will now see it inside the Object Explorer window on the Databases section.

3. Database version check via SQL editor

The user wants to check the version of the database. By right-clicking, he selects his database and then New Query.

Enter the following command in the SQL editor: select * from tpa_sysparamsys

In the Results, column of the anBuildNo, node, it reads the version of the database.

The version of the database must be known in order to download the corresponding PANTHEON software package from the FTP server.

WARNING After the database restoration, it will be necessary to transfer the users from the database to the server level. We suggest that you continue reading the Adding Users to Server Level (AddUser_PAX) section.