View source for Make a server login id (BPC RM on SQL2000)

=Introduction=

BPC RiskManager is a highly secure environment, so security setup of accounts is necessarily a little more involved than just starting up the database and the application. 


You have four options for application server login:

#. Use sa (SQL Server builtin systems administrator account)
#. Use the builtin riskmanuser user account (BPC RiskManager builtin master access account)
#. Use an account of your own choosing with administration rights.
#. Use an account of your own choosing without administration rights.


We recommend either option 1, 2 or 3 as this makes support and configuration slightly easier, and it is alread set up for you.  The easiest is to use ‘sa’ to access the database from the application server – if you are doing this you can skip the rest of this step BUT the username and password will be stored in the registry on the application server.  In a similar vein, you can create another account with systems administration rights (option 3) with the same drawback as using “sa” and the added burden of having to create the account in the first place.  The advantage of using a systems administration level account is that you do not need to do anything about access rights for the database itself.  


The generally preferred approach is option 2, using the built in user access account (or similar) with more restricted rights than ‘sa’.  The rest of this step assumes you are using riskmanuser as the database login account.  As the client components never access the database directly, the database access account is only used by the application server and the database never needs to be surfaced to any computer other than the application server, and the surveymanager host.


The databases ship with the “riskmanuser” and “mailmanager” user ids already created (the actual accounts may vary in your version - refer to the documentation shipped with your application) so if you use those ids you will find future administration easier.  These accounts have highly restricted rights (less than a normal user) and are therefore the preferred option.

<ul>
<li>	Open Enterprise Manager (SQL 2000)
<li>	Expand the folders “Microsoft SQL Servers”, “SQL Server Group” and the corresponding to the name of your computer
<li>	Expend the “Security” folder.
<li>	Right click on “Logins” and choose “New Login”
<br>
<br>
[[Image:SQLEnt_NewLogin.png]]
<br>
<br>
<li>	Select “SQL Server Authentication”
<li>	Enter a “riskmanuser” in the login name box
<li>	Enter your desired password and confirm the password
<li>	Write the password down somewhere handy as you will need it again soon.
<li>	Select “OK:
<br>
<br>
[[Image:SQLEnt_NewLogin2.png]]
<br>
<br>
</ul>


=BackLinks=

{{#dpl: linksto={{FULLPAGENAME}} }}