Create databases and users for SQL Server
You are here
- Plan for SQL Server
- Install SQL Server
- Create databases and users for SQL Server (Current task)
- Transfer SQL Server manually or Transfer between databases manually
- Verify database connections
This topic includes information on creating the recommended databases and database users in Microsoft SQL Server Enterprise Edition for IBM WebSphere Portal.
Before you begin
- You should have completed Installing SQL Server.
Notes:
- If WebSphere Portal V6.0 and an earlier version of WebSphere Portal coexist, the database user IDs for WebSphere Portal Version 6.0 must be different than earlier versions to avoid conflicts during installation.
- Database names and user information will be required when configuring WebSphere Portal to work with SQL Server.
- The tablespace LMTABLESPACE is reserved for LikeMinds. LikeMinds and Portal Personalization will drop this tablespace during uninstallation of LikeMinds and certain database transfer tasks.
Create databases
Before you create the database users, create the databases. Use the SQL Server Enterprise Manager to create the databases.
- Expand the nodes to see Databases.
- Right-click on Databases to see New database.
- Enter the database name. For information on the recommended database architecture and the databases create, see Planning for SQL Server.
- Select the Collation Name from the drop-down list according to the environment. Verify that collation is set to case-sensitive. For example, on an English system:
- SQL_Latin1_General_CP1_CS_AS
For LikeMinds, CI is the default setting; however, CS can also be used.
- Click OK to save the database changes.
Create database users
After creating the databases, create the recommended database users with the SQL Server Enterprise Manager.
- Connect to the SQL Server instance.
- Expand the tree view beneath the SQL Server instance.
- Expand Security and right-click on Logins.
- In the opening context menu, select New Login....
- Enter the database user names. For information on the recommended database architecture and the databases create, see Planning for SQL Server.
- Select SQL Server Authentication.
- Set a password for the selected user.
- In the "Database Access" pane, select the database the user must connect to at runtime. The following mappings are recommended:
Database User RELEASE RELEASEUSR COMMUNITY COMMUNITYUSR CUSTOMIZATION CUSTOMIZATIONUSR WMM WMMDBUSR JCRDB ICMADMIN FDBKDB FEEDBACK LMDB LMDBUSR
- Be sure that no Server Role is selected.
- Set Database Access as follows:
Database User Database Role RELEASE RELEASEUSR WMMDBUSR public db_owner COMMUNITY COMMUNITYUSR public db_owner CUSTOMIZATION CUSTOMIZATIONUSR public db_owner JCRDB ICMADMIN public db_owner FDBKDB FEEDBACK public db_owner LMDB LMDBUSR public db_owner WMM WMMDBUSR public db_owner
- Click OK to save the user changes.
Set SQL Server properties Authentication
After creating the databases and users, set the SQL Server Enterprise Manager Authentication setting to SqlServer and Windows. This will eliminate the need for run-time authentication of SQL Server requests.If you have previously configured these settings on Enterprise Manager, you do not need to complete these steps.
- Open the SQL Server Enterprise Manager by selecting...
Start menu | Programs | Microsoft SQL Server | Enterprise Manager
- Expand the tree control until we can see the server.
- Right click on the server name and select Properties. The "SQL Server Properties (Configure)" window will open.
- Select the Security tab.
- For Authentication, select SQL Server and Windows.
- Restart the SQL Server to apply the update.
Next steps
You have completed this step. Continue to the next step:
Parent topic:
Create databases and users