Installation and Configuration › How to Prepare Your DBMS Environment › Tasks to Create a Microsoft SQL Server DBMS › Microsoft SQL Server 2005 Permissions

Microsoft SQL Server 2005 Permissions

For SQL Server 2000, you only need the public permission assigned to save to the mart. However, when the repository is on an SQL Server 2005 instance, you must have the bulkadmin permission designated as well. The ability to do bulk inserts (which was permitted by the public permission, previously) is no longer part of the public permission. As the administrator, you must explicitly define this permission or when you attempt to save a model to a new mart created using a SQL Server 2005 database, an error "You do not have permission to use the bulk load statement." is returned.

Tasks to Create a Sybase DBMS

The following tasks must be performed by the DBA and system administrator responsible for installing the software on a Sybase database management system. Information provided in this section includes installation and Sybase connectivity software requirements.

1. Use a graphical user interface (GUI) tool, ISQL (all versions), SQL Administrator, Sybase Central Java, or Enterprise Manager to create the CA ERwin MM database. If a GUI tool is not available, you can use ISQL to type in the appropriate commands manually.

   Your database should meet the following criteria:

   • The size of the data device you create determines the size of the database. The minimum database size is 32 MB so there has to be at least one device that is 32 MB. You should also locate the data device on a different disk (and disk controller) than the transaction log.
   • For optimum performance, ensure that separate devices are used to store the data and the transaction log. For example, you can increase performance by creating a 50 MB data device and a 25 MB log device. A minimum of 40 MB of disk space (data and log) is required.
2. Add users.

   For users to access the mart you must either add existing logins as users to the database or create new logins and add them as users of the database. A login is an entity permitted to connect to the database server; a user gives a login the right to use a particular database. If you use Windows user names and passwords to secure database access (Windows Authentication), you must add the Windows users to your DBMS.

3. Check the Stored Procedure Cache.

   Set the Stored Procedure Cache size to at least 8 MB. Setting it higher improves performance, especially when many users are accessing the server concurrently. Setting it lower results in fatal errors and rollbacks when the Stored Procedure Cache size is exceeded.

   Note: The installation creates more than 100 stored procedures. The CA ERwin MM client invokes these stored procedures to control changes to the data in the database.

4. Check tempdb size.

   Significant temporary space is required for installation and use. The temporary segments need at least 16 MB of available space. You should also increase available space as the number of concurrent users increase.

5. Check memory allocated to the database server.

   Allocate at least 32 MB of RAM to the database server. The amount of RAM allocated should be half of the available RAM on the server.