Database Creation & Setup for SQL Server

Transcription

1 Database Creation & Setup for SQL Server INSTALLATION MANUAL D rev 4.0

2 TRADEMARK NOTICE Bentley and the "B" Bentley logo are registered or non-registered trademarks of Bentley Systems, Inc. or Bentley Software, Inc. All other marks are the property of their respective owners. COPYRIGHT NOTICE Bentley Systems, Incorporated. All Rights Reserved. Including software, file formats, and audiovisual displays; may only be used pursuant to applicable software license agreement; contains confidential and proprietary information of Bentley Systems, Incorporated and/or third parties which is protected by copyright and trade secret law and may not be provided or otherwise made available without proper authorization. RESTRICTED RIGHTS LEGENDS If this software is acquired for or on behalf of the United States of America, its agencies and/or instrumentalities ("U.S. Government"), it is provided with restricted rights. This software and accompanying documentation are "commercial computer software" and "commercial computer software documentation," respectively, pursuant to 48 C.F.R and , and "restricted computer software" pursuant to 48 C.F.R (a), as applicable. Use, modification, reproduction, release, performance, display or disclosure of this software and accompanying documentation by the U.S. Government are subject to restrictions as set forth in this Agreement and pursuant to 48 C.F.R , , , and , as applicable. Contractor/Manufacturer is Bentley Systems, Incorporated, 685 Stockton Drive, Exton, PA Unpublished - rights reserved under the Copyright Laws of the United States and International treaties. Bentley Systems, Incorporated 685 Stockton Drive Exton, PA BENTLEY ( ) eb Insight version 15 Database Creation & Setup for SQL Server Published by Bentley Systems, Inc. Information in this document is subject to change without notice and does not represent a commitment on the part of Bentley Systems, Inc. The software and/or databases described herein are provided under a license agreement or nondisclosure agreement. The software and/or databases may be used or copied only in accordance with the terms of the agreement. It is against the law to copy the software on any medium except as specifically allowed in the license or non-disclosure agreement. The purchaser may make one copy of the software for backup purposes. No part of this manual and/or databases may be reproduced or transmitted in any form or by any means, electrical or mechanical, including photocopying, recording, or information recording and retrieval systems, for any purpose other than the purchaser's personal use, without the express permission of Bentley Systems, Inc. Unless otherwise noted, all names of companies, products, street addresses, and persons contained herein are part of a fictitious scenario or scenarios and are designed solely to document the use of the product. page ii

3 Table of Contents Installation Road Map...1 Pre-Requisites...2 Create a New Microsoft SQL Server Database...2 Creating a Login ID for the Database...6 Enabling Remote Connections...10 Next Step...11 page iii

4 List of Figures Figure 1: SQL Server management studio... 2 Figure 2: New database... 3 Figure 3: Creating datafiles... 4 Figure 4: Database properties... 5 Figure 5: Database options... 6 Figure 6: Populated new database user, general page... 7 Figure 7: Server roles, public selected... 8 Figure 8: User mappings, db_owner selected... 9 Figure 9: Granting execute permissions Figure 10: SQL Server Configuration Manager page iv

5 Installation Road Map D Rev 4.0 feb12 page 1

6 Pre-Requisites eb Database Creation & Setup for SQLServer It is assumed that you have already performed the following steps: Installed Microsoft SQL Server 2005 or 2008 R2 using the default options for all prompts EXCEPT when prompted. Enable mixed mode authentication during the install. If using SQL 2005, SP2 should be installed, and also the following patch: Note: Microsoft SQL Server 2000 is no longer supported. Important: Perform all installations logged on as a member of the domain, with at least Administrator rights to the Windows 2003/2008 Server, and preferably with Domain Administrator rights. Create a New Microsoft SQL Server Database Go to Start > All Programs > Microsoft SQL Server 2005/8 > SQL Server Management Studio. After a successful login, the following window is displayed: Figure 1: SQL Server management studio 1. Go to <machine_name> and right-click the Databases folder. 2. Select New Database from the pop-up menu. The Database Properties window is displayed. Enter the name of the database you want to create. (For purposes of this document we will use eb as the database name.) 3. Write the name of the database in the "Database Name" section of the eb Installation worksheet. D Rev 4.0 feb12 page 2

7 Figure 2: New database 4. Scroll to the right and use the Path column to change the location of the database if desired. Otherwise just accept the default paths. Note to DBA: An empty eb database takes 40Mb of data. As the size of data depends on the amount of documents, associations and index data used at a site the best method for sizing is data from a Test or Training database configured to your site s specifications. If this is not possible a small database of 100Mb to 200Mb will have enough space so that sizing can be accomplished at a later date. 5. Create the transaction logs as 15-25% of the datafile, add more space if the log files are kept after the transaction is complete for recovery purposes. D Rev 4.0 feb12 page 3

8 Figure 3: Creating datafiles 6. Click OK to Create the Database. 7. Edit the New Microsoft SQL Server Database Properties. Right-click the new database and open the Properties window of the newly created database. Options and Permissions are now available: D Rev 4.0 feb12 page 4

9 Figure 4: Database properties 8. Click the Options page and review the defaults: Settings: Auto update statistics - True Auto Create Statistics - True. D Rev 4.0 feb12 page 5

10 Figure 5: Database options Note to DBA: eb requires "Auto update statistics", "Auto create statistics" and the database not be marked Read-only. Recovery mode can be changed. ANSI NULL default should not be checked. In the OBDC settings "ANSI nulls" must be unchecked and "Use quoted identifiers" needs to be checked. 9. Click OK to save the changes. Creating a Login ID for the Database 1. You can access the database using either windows authentication or a SQL Server Login ID. 2. To create a SQL Server login, within Microsoft SQL Server Management Studio, go to <database_server>. 3. Expand the folder named Security. 4. Right-click the Logins folder and select New Login from the pop-up menu. The Microsoft SQL Server Login Properties-New Login window is displayed. D Rev 4.0 feb12 page 6

11 Figure 6: Populated new database user, general page 5. Enter the name of the SQL Server user on the General page screen. 6. Enter your chosen name in the 'Database login username' field of the eb Installation Worksheet. 7. You can select Windows Authentication or SQL Server authentication depending upon your preferences. In the following, it is assumed that SQL Authentication has been selected. 8. Enter a password for the new user. 9. Enter your chosen password in the 'Database login password' section of the eb Installation Worksheet. 10. Select the default database from the drop-down list, choose the database noted under 'Database Name' from the eb Installation Worksheet. 11. Specify the default language for the user. Note: Do not choose OK at this point. 12. Click the Server Roles page. These roles are global on the SQL server instance for that user, i.e. if you have setupadmin/serveradmin/sysadmin you can create/drop db's etc. 13. Confirm that public is selected. D Rev 4.0 feb12 page 7

12 Figure 7: Server roles, public selected Important: The setupadmin role (or sysadmin) is only required when configuring FTR when a link is created between the SQL server and the Indexing service. Once this is done, the role can, and should, be revoked. 14. Click on the User Mappings page. This allows mapping of your new user to your previously created database. 15. We recommend that you have the db_owner database role as minimum. This makes the user the owner of the database used by eb only and can change the database as required. In the 'Database role membership for user_name'. Check the "db_owner" box. Note: The 'Public' box will already be checked. D Rev 4.0 feb12 page 8

13 Figure 8: User mappings, db_owner selected 16. If Database Administrators resist assigning db_owner permissions, then read carefully: As a minimum you want db_datareader & db_datawriter. To be able to run the database update scripts, the user that will be doing this with the SMC needs to have db_ddladmin as well as db_datareader/writer. You also need the EXECUTE permission. This gives you permissions to execute procedures, do selected statements, inserts, deletes etc. with the data. Without the above you cannot even login because we already need to write data at this point. To grant the execute permission, go to the Properties of your database, and click on the Permissions page. This allows specifying the exact permissions you can assign, the database roles from previous setup is just a predefined list of these permissions. Click the 'Effective Permissions' button to get a list of permissions that the user has which it got from the database roles plus what is selected here. Highlight your user, and grant Execute Permissions. Without the Execute permissions, you will get a message similar to: The EXECUTE permission was denied on the object 'ebp_logon', database 'eb', schema 'dbo'. D Rev 4.0 feb12 page 9

14 Figure 9: Granting execute permissions Enabling Remote Connections To enable remote connections (if required): Note: By default, SQL Server 2005/2008 Express, Evaluation, and Developer editions allow local client connections only. Enterprise, Standard, and Workgroup editions also listen for remote client connections over TCP/IP. 1. Start > All Programs > Microsoft SQL Server 2005/2008 > Configuration Tools > SQL Server Configuration Manager. 2. In SQL Server 2008, expand 'SQL Server Network Configuration', or in SQL Server 2005 'SQL Server 2005 Network Configuration' and highlight Protocols for MSSQLSERVER. D Rev 4.0 feb12 page 10

15 Figure 10: SQL Server Configuration Manager 3. Ensure that your required protocol is enabled, usually TCP/IP. Next Step The next step of the installation is 'eb Server Installation Manual.' D Rev 4.0 feb12 page 11