Microsoft KB Archive Search

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.

  1. Home
  2. How to create a SQL Server user account that corresponds to a Microsoft Forecaster user account

How to create a SQL Server user account that corresponds to a Microsoft Forecaster user account

View products that this article applies to.

INTRODUCTION

This article describes how to create a Microsoft SQL Server user account that corresponds to a Microsoft Forecaster 7.0 user account. To do this, you must have access to SQL Server Enterprise Manager or SQL Server Management Studio.

↑ Back to the top

More Information

Follow these steps on the server that is running SQL Server and that contains the Microsoft Forecaster database:
  1. Start SQL Server. To do this, follow the appropriate step:
    • To start SQL Server 2000, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager for SQL Server 2000.
    • To start SQL Server 2005, follow these steps:
      1. Click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio for SQL Server 2005.
      2. Enter a user account and a password for an account that has system administrator rights. For example, log on as the sa user.
      3. Click Connect to Database Engine.
  2. Expand server_name, and then expand Security.

    Note server_name represents the actual server name.
  3. Right-click Logins, and then click New Login.
  4. Enter a user name for SQL Server. To do this, follow the appropriate step:
    • In SQL Server 2000, type the user name in the Name box.
    • In SQL Server 2005, type the user name in the Login box.
  5. Enter a password. To do this, follow the appropriate step:
    • In SQL Server 2000, click Windows Authentication or SQL Server Authentication. If you click SQL Server Authentication, type a password in the Password box.
    • In SQL Server 2005, click Windows Authentication or SQL Server Authentication. If you click SQL Server Authentication, type a password in the Password box. Then, retype the password in the Confirm password box.
  6. Select the Microsoft Forecaster database. To do this, follow the appropriate step:
    • In SQL Server 2000, click the Database Access tab, and then click the Microsoft Forecaster database.
    • In SQL Server 2005, click the User Mapping tab, and then click the Microsoft Forecaster database.
  7. Grant access to the Microsoft Forecaster database. To do this, follow the appropriate step:
    • In SQL Server 2000, click the Microsoft Forecaster database, select the Permit check box, and then select the Public check box and the Forecaster check box in the "Permit in Database Role" window.
    • In SQL Server 2005, follow these steps:
      1. Click the Microsoft Forecaster database.
      2. Select the Map check box.
      3. In the Default Schema column, click the ellipsis button (...).
      4. In the Select Schema window, click Browse.
      5. In the "Browse for Objects" window, select the Forecaster check box, and then click OK two times.


        Note You expect Forecaster to be listed as the Default Schema.
      6. In the "Database role membership for" window, select the Public check box and the Forecaster check box.
  8. Click OK.
  9. In the Confirm new password box, type the password.


    Note This step applies only to SQL Server 2000.



Note The Great Plains logins cannot be used for Forecaster. Forecaster can not read the Great Plains password encryption. This is documented in KB 962701 .

↑ Back to the top

Keywords: kbexpertiseinter, kbhowto, kbmbsmigrate, kbexpertisebeginner, kbmbspartner, kbexpertiseadvanced, kb, kbgreatplainsfrx, kbnavisionfrx, kbsolomonfrx, kbaxaptafrx

↑ Back to the top

Article Info
Article ID : 946873
Revision : 3
Created on : 4/23/2018
Published on : 4/23/2018
Exists online : False
Views : 335