1.1 Basic information for installing Microsoft SQL 2008 R2 SP2, path to installation software,

Transcription

1 OMEGA FOR MS SQL CONTENT 1 BASIC INFORMATION 1.1 Basic information about Microsoft SQL 2008 R2 SP2 and 2012 installation, path to installation software, possible restrictions, Omega software licence 1.2 Server hardware and software requirements 1.3 Manual installation and conversion steps of Omega database from Access to MS SQL 2 INSTALLATION OF Microsoft SQL 2.1 Installation of Microsoft SQL 2008 R2 SP2 2.2 Installation of Microsoft SQL Configuration of SQL server and access rights 3 CONVERSION of OMEGA to SQL 3.1 Conversion of database from Access to SQL 3.2 Attaching clients 3.3 Reinstallation of SQL server or transfer of databases to a different server 3.4 Support files sharing 4 BACKUP AND RESTORING OF DATABASE USING MANAGEMENT STUDIO 4.1 Database backup 4.2 Database restoring 5 AUTOMATIC BACKUP for Microsoft SQL 2008 R2 SP2 1 BASIC INFORMATION 1.1 Basic information for installing Microsoft SQL 2008 R2 SP2, path to installation software, possible restrictions, Omega software licence If you have a large database, i. e. more than 90 MB, or four or more users are working with the Omega software at the same time, an installation of Microsoft SQL is recommended for smooth running of the Omega software. To work with the Omega software you only need a free version of Microsoft SQL 2008 R2 SP2. Restrictions: use of 1GB RAM at the most, the size of the database can be 8 GB at the most. Microsoft SQL 2008 R2 SP2 installation files, which already contain the Management Studio, can be downloaded from the Microsoft internet page or from the Kros FTP server or they can be installed from the support DVD. The files are SQLEXPRWT_x86_ENU.exe * (for 32 - bit operating systems) or SQLEXPRWT_x64_ENU.exe * (for 64 - bit operating systems), and they already contain the SQL Server itself as well as the Management Studio. Path to the Microsoft SQL 2008 R2 SP2 installation program on the support DVD: /Servis/SQLServer/SQL 2008 R2 Express SP2/. Besides Microsoft SQL 2008 R2 SP2 we also support Microsoft SQL Server 2012 Express SP1. The Microsoft SQL Server 2012 Express installation files can be downloaded from the Microsoft internet page or from the Kros FTP server or they can be installed from the support DVD. The files are SQLEXPRWT_x86_ENU.exe * (for 32 bit operating systems) or SQLEXPRWT_x64_enu.exe * (for 64 bit operating systems). Path to the Microsoft SQL 2012 Express SP1 installation program on the support DVD: /Servis/SQLServer/sql 2012 Express sp1/. Using Microsoft SQL 2014 is also a possibility. Microsoft SQL Server 2014 Express installation files can be downloaded directly from the Microsoft internet page or from the Kros FTP Strana 1 z 19

2 server or they can be installed from the support DVD. The files are SQLEXPRWT_x86_ENU.exe * (for 32 bit operating systems) or SQLEXPRWT_x64_enu.exe * (for 64 bit operating systems). Path to the Microsoft SQL 2014 Express installation program on the support DVD: /Servis/SQLServer/SQL 2014 Express/. *The installation file can be downloaded directly from our server by clicking the file name. Authentication information needs to be filled in after the click: user name: password: omeuziv nivea5uz Note: The images below are intended for the Microsoft SQL 2008 R2 SP2 installation. For the operating systems Windows 8 and Windows Server 2012 we recommend to install MS SQL Server 2012 SP1 or MS SQL Server If you want to install MS SQL Server 2008 R2 SP2 on these operating systems, please visit the Microsoft page for more information. If you have Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows Server 2008, Microsoft Windows Server 2008 R2, Microsoft Windows 2012, you can install Microsoft SQL 2008 R2 SP2 directly. If you have an older operating system (Vista, Server 2003), the SQL installation requires that Microsoft.NET Framework 3.5 SP1 or its higher version, Windows Installer 4.5 and Power Shell 1.0 was already installed. If no SQL sever has been installed on the PC so far, we recommend to install it as a default instance (the name of the SQL server will be the same as the name of the PC). If you are going to install another SQL server on the PC, you need to use a named instance (the name of the SQL server will be NameOfPC/NameOfInstance ). Omega software licence: A special licence of Omega software for SQL (about 100% Omega price increase) is needed by those customers who bought the Omega software licence for more than 6 PCs and more than 6 users at the same time. 1.2 Server hardware and software requirements: Server is a reserved PC, which is not regularly used with client applications (Word, Excel, Outlook...). Dual-core processor 2,4 GHz, 4 GB RAM, SSD data disk. Name of the PC - only letters of English alphabet without diacritics, it means no dashes, commas, accents and other characters. Operating system at least Microsoft Windows Vista, Windows 7 Professional, Microsoft Windows 8, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Server 2008, R2 or Microsoft Windows Server For Omega software data, i.e. where mdf a ldf files are stored, you need to add a new directory in the root of the disk (for example C:\SQLData). No diacritic or space, etc. can be used in the directory name. Only the English alphabet letters can be used. Regional and Language Options have to be set to Slovak. Software firewall has to be turned off on the server, or an exception for port 1433, through which the SQL server communicates, has to be added. Terminal connection: To work with the Omega software we support Remote Desktop Connection or Terminalserver. We do not support RemoteApp. 1.3 Manual installation and conversion steps of Omega database from Access (.mdb) to MS SQL (.mdf) Install a version of the SQL server using the section 2.1. Configure the SQL server and access rights using the section 2.3. Install the OMEGA software to the server. Convert the databases from Access to SQL using the section 3.1. Attach Omega clients to SQL databases using the section 3.2. Strana 2 z 19

3 2. INSTALLATION OF MICROSOFT SQL 2.1 Installation of Microsoft SQL 2008 R2 SP2 Installation process of the SQL server is shown in the following images: Image 1 Image 2 Image 3 Image 4 Strana 3 z 19

4 Image 5 Image 6 Image 7 Image 8 Image 9 Image 10 Strana 4 z 19

5 Note: Mixed Mode means that the clients can have an access to SQL server through the windows authentication (a user can log in to the Management Studio without entering the password) or through the SQL server authentication (an access to the Management Studio has the administrator who logs in using the password that was entered in the Enter password box and Confirm password box during the installation of the Microsoft SQL 2008 R2 SP2). Image 11 Image 12 Image 13 After the installation of Microsoft SQL 2008 R2 SP2 continue using the section 2.3 Configuration of SQL server and access rights and the section 3. Conversion of Omega to SQL. Note: The tool for managing the SQL server, which is the SQL Server Management Studio, is automatically installed with the installation of the SQL server. Strana 5 z 19

6 2.2 Installation of Microsoft SQL 2014 Installation process of the SQL server is shown in the following images: Image 1 Image 2 Image 3 Image 4 Note: You can choose between a Default instance and a Named instance (image 4). If a different version of the SQL server was installed, you need to choose the Named instance. Installed instances can be seen in the table of the image 4. Strana 6 z 19

7 Image 5 Image 6 Image 7 Image 8 Note: Mixed Mode means that the clients can have access to SQL server through the windows authentication (a user can log in to the Management Studio without entering the password) or through the SQL server authentication (an access to the Management Studio has the administrator who logs in using a password that was entered in the Enter password box and Confirm password box during the installation of the Microsoft SQL 2008 R2 SP2). After the installation of the Microsoft SQL 2014 continue using the section 2.3: Configuration of SQL server and access rights and the section 3.: Conversion of Omega to SQL. Note: The tool for managing the SQL server, which is the SQL Server Management Studio, is automatically installed with the installation of the SQL server. Strana 7 z 19

8 2.3 Configuration of SQL server and access rights During the installation of the SQL server so called mixed mode was used, which means that the clients can have access to the SQL server through the windows authentication or through the SQL server authentication. You set the access rights according to the choice of access or according to the type of network the SQL is in. There are three possibilities of connecting in the current version of the Omega software: a) Trusted connection is the access through the windows authentication. Check the type of the network first. This is done by using the My Computer Properties icon. In case the network is a domain (i.e. winkros.local), it is necessary to add each member of the domain to the users of the SQL server (in SQL server Management Studio a Security/Logins part needs to be expanded in the tree structure and a new user is added using a right click of a mouse - New Login). If the network is a workgroup type, then a Guest account needs to be enabled and added to the users of the SQL server. Steps to enable the Guest account: Right click on My Computer Computer Management. Then you click on Local Users and Groups Users. In the right part of the window find the Guest account. In the tab called General uncheck the box Account is disabled. To enable the Guest account click on OK. The Guest account can also be enabled through Control Panel Users. In case of a terminal server, all users, who will be working with the Omega software on the terminal server, need to be added to the SQL server users. b.) Systémový účet Omegy is the access through the SQL authentication. The Omega software creates such account while connecting the first client and the clients will be connected through this account. c.) Vlastný užívateľ is the access through the SQL authentication. A new account needs to be created using the Management Studio and then used to connect the clients to the Omega database. IMPORTANT: All accounts (no matter which one of a.), b.) or c) was chosen) must have a box sysadmin checked in Server Roles! Strana 8 z 19

9 SUGGESTION: After installing the SQL Server, the protocols Named pipes and TCP/IP are turned off by default. It is required to turn them on after the installation and then restart the SQL server service. In this case we work with the SQL Server Configuration Manager. Path to the settings: Start Programs Microsoft SQL Server 2008 R2 Configuration Tools SQL Server Configuration Manager. Image 1 Image 2 Strana 9 z 19

10 3. CONVERSION OF OMEGA TO SQL 3.1 Conversion of database from Access to SQL For a fast conversion of the database and a better performance of some operations in Omega we recommend to install DTS libraries, which are not included in Microsoft SQL 2008 R2 SP2. These libraries are: SQLServer2005_bc_x32.msi for the 32-bit version of the SQL Server and SQLServer2005_bc_x64.msi for the 64-bit version of the SQL Server (they can be downloaded from the Microsoft page or from our FTP: /Servis/SQLServer/Microsoft SQL 2008 R2 SP2/DTS/ or directly by clicking the name of the file). Authentication information for a direct download from our server is: user name: password: omeuziv nivea5uz Conversion of the access database (.mdb) to the SQL database (.mdf) should be done on the SQL server. Create a new folder on your hard drive where the SQL database of a company will be stored. IMPORTANT: Create the folder as a main folder on one of the hard drives of the SQL server (not a subfolder), and the name of the folder should be composed of the letters of English alphabet and as short as possible, e.g. D:\data alebo D:\sqldata. In this folder create some subfolders for individual companies with the names composed of 5-10 characters (only the letters of English alphabet, no dashes, commas and other special characters). IMPORTANT: If clients` PCs are going to be connected to the SQL server, it is required that sharing of folders for writing and reading for all Omega users is turned on (so called full rights). More information can be found in the section 3.4 Support files sharing. Copy the.mdb file extension database you are using and going to convert to the SQL database (usually stored on C:\Omega\data\name of company) to the folder that has just been created. Disconnect the connected database (Omega Pripojené firmy) and then connect it again from the newly created folder (D:\SQLdata\name of company). Choose Omega Pripojené firmy from the main menu. Choose the database of the company you are going to convert. Finnish the conversion process using Funkcie Prevod databázy Prevod Access SQL. The steps are shown in the images below. Steps of the conversion of the database: Image 1 Image 2 Image 3 Strana 10 z 19

11 Write the name of your SQL server in the SQL Server field and choose the type of connection (window in Image 3). Image 4 Image 5 A company is opened from the main menu using Firma Otvor and the database can be used as usual. 3.2 Attaching clients In the software, all users need to be detached from the access database and attached using Na SQL button. You have to state the name of the SQL server and the way of connecting (Trusted, ). When connecting more databases, providing a successful connecting of the first database, Omega will offer the name of the SQL server in the expanding menu. 3.3 Reinstallation of SQL server or transfer of databases to a different server If there is a reason to reinstall the SQL server or you need to transfer the databases from one PC to another, it is required to also have the SQL server installed in the computer, which the databases will be transferred to, following the previous steps of installation. In case of the same version of the SQL server on both computers, the transfer is done in two steps: Unregistering the database from the original server in the Management Studio using detach (Image 1 below). Registering the database with a new server in the Management Studio using attach (Image 2). IMPORTANT: Select the database marked with the ID code of the company that is being detached and right click on it when unregistering the database in the Management Studio. The ID code can be found in the attached companies (Omega Pripojené firmy). Strana 11 z 19

12 Unregistering a database Image 1 Registering a database: After the installation of the server and before the first connection to a new server, it is required to convert the database from Access to SQL. You can convert any database, for example skúšobný príklad, and the conversion provides saving of the stored procedures required for running of the Omega software on the SQL server. To connect the database use the MS SQL Server Management Studio (you can run the program using Start Programs SQL Server Management Studio). SUGGESTION: Save the.mdf and.ldf files that belong to the SQL database of the company to your PC. Image 2 IMPORTANT: For technical reasons it is not possible to transfer a database from a higher version to a lower version of the SQL server. Use the archive of the Omega software when transferring the database from the lower to the higher version of the SQL server. Strana 12 z 19

13 3.4 Support files sharing For a proper running of the Omega software across the network, it is required to have a folder created that will be available to read and write for all the users that access the database on the SQL server. The first option is to fully share the database folder created in the section 3.1 (for example D:\SQLdata\). The second option is to create a new folder with the name vlastný adresár pre pomocné súbory or pomocný adresár in the Omega software. Its advantage is in that the files of databases are not free to access over the network which increases their security. Analogically, a pomocný adresár folder can be created as a database folder: a. Create the folder in the root of the disk as a main folder. b. Use the letters of English alphabet only, don`t use any special characters or spaces. c. Make subfolders for individual companies in the folder. Folders in the form of, for example D:\OMEGATEMP\NameOfCompany\, are generated. d. Share the main folder (D:\OMEGATEMP\) through Properties Sharing Advanced sharing check Share This Folder (never change the Share name!!!!) Permissions. Allow the Full control in the next window for all users using the Omega software, the easiest is to use the group Everyone. e. Then it is required to set the pomocný adresár in EACH!!! database of the Omega software using the menu Firma Nastavenia Všeobecné nastavenia and then Firma Vlastný adresár pre pomocné súbory. There has to be a different subfolder for each company. Use the same subfolder for different accounting periods (years). Strana 13 z 19

14 4. BACKUP AND RESTORING OF DATABASE USING MANAGEMENT STUDIO 4.1 Database backup To back up a database is one of the MOST IMPORTANT steps, that prevents some unexpected situations, leading to the loss of the data, from happening. We suggest the following steps to follow when backing up the database using the Management Studio. 1. Open the Management Studio. Then click on Databases. You will see the list of databases you choose from. Select a database and then right click on it. Click on Tasks, and then Back Up The Back Up Database window appears. If you want to change the backup file, click the Remove button and then the Add button. The Select Backup Destination window appears, and you need to click the button with the three dots. Then the window Locate Database Files pops up. Choose All Files (*) in the expanding menu in the bottom part of the window (Files of type) and select the file for the backup destination, then OK. If you don t want to change the backup file, just click OK. Strana 14 z 19

15 3. The Select Backup Destination window opens. The target file, in which the backup file should be created, can be found in Destinations on disk. Click OK. 4. The Back Up Database window pops up and the target file will be in Destination Back up. Click OK. Strana 15 z 19

16 5. The software gives a notification about a successful completion of the database backup. 4.2 Database restoring If there is a loss or damage of data of a company, it is possible to have the data restored using the backup that was done previously. If the restoring is done using the Management Studio, you can take the following steps. These steps can be taken only in case the database was backed up using the Management Studio, it is not possible to restore the database created in the Omega software (menu Firma Archivuj). 1. Open the Management Studio. Then right click on Databases and then Restore Database. 2. In the Restore Database window select From device. Click on the button with the three dots that is on the right in the same line. The Specify Backup window appears and you click Add. The window displayed is used to search for the backup file you want to restore. Choose All Files (*) in the expanding menu in the bottom part of the window (Files of type). Select the backup file you want to restore and click OK. Strana 16 z 19

17 3. The chosen backup file automatically appears in the Specify Backup window in the Backup location field. Click OK. 4. After clicking OK in the previous window the backup file appears in the Restore Database window. Select Restore in the Select the backup sets to restore field. Write the correct name of the database that is being restored to the To database field or chose the database directly from the expanding menu. The database has to have the form of x_yyyyyyyyy, where the number of the database being restored (YYYYYYYYY) is the ID number of the Omega database. Then click OK. The software notifies that the restore of the database was completed successfully. Strana 17 z 19

18 5. IMPORTANT: Using the Management Studio all databases, which were backed up using a lower or the same version of the SQL Server, are restored. In case your computer contains a lower version of the SQL server than the version of the SQL server the backup database was created in, the database cannot be restored and the software reports an error. In such cases it is required to install the same or a higher version of the Management Studio and he SQL server the backup database was created in. 5. AUTOMATIC BACKUP for Microsoft SQL 2008 R2 SP2 Besides the manual backup using the Management Studio, there is also a possibility of the automatic backup of the database using the SQL server tools. backup.sql a backup.bat files are used for backup there. 1. The first file is backup.sql. Backup.sql is a command that performs a backup of the database on the SQL server: BACKUP DATABASE [x_ ] TO DISK = N'D:\zalohaSQL\x_ bak' WITH NOFORMAT, INIT, NAME = N'x_ Full Database Backup', SKIP, NOREWIND, NOUNLOAD, STATS = 10 GO where x_ is the name of the SQL database, D:\zalohaSQL folder, in which the backup.sql, backup.bat files are stored, backs up the database and also saves the backupinfo.txt file info about the backup result. You can choose any name of the folder, it is entirely up to you. x_ bak is the name of the backup. Again, you can choose any name for it. IMPORTANT: The above mentioned parameters can be adjusted to your needs. You can back up more databases. You can repeat the BACKUP a GO commands for every new database. 2. The other file is backup.bat. Backup.bat starts backup.sql using the utility SQLCMD.EXE. Commands in backup.bat: C: CD C:\Program Files\Microsoft SQL Server\100\Tools\Binn\ SQLCMD.EXE -S MenoSQLServera -E -i D:\ZalohaSQL\backup.sql -o D:\ZalohaSQL\backupinfo.txt D: CD D:\ZalohaSQL\ A backup of a database can be planned. You choose when Windows will perform this task. Go to Start Control Panel System and Security Administrative Tools Schedule Tasks Create Basic Task and the Basic Task Wizard opens. Strana 18 z 19

19 IMPORTANT: The software will overwrite the created backups. By combining more tasks in the task scheduler and by changing of backup file names it is possible to achieve that more backups with different names are saved (for example every day of the week). Strana 19 z 19