Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Forecaster 7.0 Permissions in SQL Server 2005


View products that this article applies to.

More Information

Please step through the following instructions to review and correct Forecaster 7.0 permissions in SQL Server 2005 by launching SQL Server Management Studio.

Review the Forecaster schema:
  1. Click on the Databases folder to expand the list of databases restored on this server.
  2. Click on the Forecaster 7.0 database name to expand the folder.
  3. Click on the Security folder to expand security components for this database.
  4. Click on the Schemas folder to expand the schema list.
  5. Double-click the Forecaster schema to review its setup.
    1. On the General page, click on Search next to Schema Owner.
    2. Click the Object Types button and select Database Roles only.
    3. In the Search Roles and Users window, type Forecaster in the Object Types window and click Check Names. The Forecaster role should be confirmed. Click OK.
  6. Click OK to close the schema window.
Review the Forecaster role:
  1. Click on the Roles folder under the Forecaster 7.0 database name to expand it.
  2. Click on the Database Roles folder to expand the list
  3. Double-click the Forecaster role to review its setup.
    1. Check that the Owner is dbo.
    2. Under Owned Schemas, make sure that the Forecaster schema is the only one checked.
    3. Review the Role Members group to ensure that the Forecaster users are included here.
Review the Forecaster role permissions on the Forecaster 7.0 database:
  1. Click on the Forecaster 7.0 database name.
  2. Right-click and select Properties.
  3. Click on the Permissions page.
  4. Click on the Forecaster database role in the Users and Roles section of this page.
  5. Scroll down through the explicit permissions window to locate the Create Table and Create Procedure permissions.
  6. Both of these must have the Grant permission checked.
Review the Forecaster table ownership:
  1. Click on the Tables folder under the Forecaster 7.0 database name to expand the list of defined tables.
  2. Confirm that the tables are owned by the dbo user. The tables with very long names are temporary tables that are owned by the individual users logged into the application. These tables do not have to be owned by dbo.
  3. If the tables are not owned by dbo, contact Microsoft Forecaster Support for additional information.
Review the DBO schema:
  1. Click on the Forecaster 7.0 database name to expand the folder.
  2. Click on the Security folder to expand security components for this database.
  3. Click on the Schemas folder to expand the schema list.
  4. Double-click the dbo schema to review its setup.
    1. Click on the Permissions page.
    2. The Users or Roles section will contain the Forecaster role. If it does not exist, click the Add button.
    3. In the Select Objects and Roles window, click Object Types.
    4. Click on the Database Roles checkbox and click OK.
    5. Type in Forecaster and click on Check Names to confirm. Click OK to close this window.
    6. In the section entitled Explicit permissions for Forecaster, the GRANT permission must be selected for the following actions: Delete, Insert, Select, Update.
Review the Forecaster users setup in SQL Server 2005:
  1. Click on the Security folder for SQL Server 2005 (not under the Forecaster 7.0 database name).
  2. Click on the Logins folder to expand the user list.
  3. Double-click on the Forecaster 7.0 userid to review the setup.
    1. Click the User Mapping page.
    2. Select the checkbox next to the Forecaster 7.0 database.
    3. In the Database Role Membership section, check the public and Forecaster roles. If the user is a budget administrator within the Forecaster application and will be creating or modifying periods, the user must have the db_owner role. This additional permission should be limited to a few select individuals, and not given to all users defined in the Administrator security group within the application.
      For Administrator users, the Default Schema should be DBO.

      For Non-administrator users, the Default Schema should be Forecaster.

↑ Back to the top


References

↑ Back to the top


Keywords: kbnosurvey, kb

↑ Back to the top

Article Info
Article ID : 962517
Revision : 3
Created on : 3/30/2017
Published on : 3/30/2017
Exists online : False
Views : 309