Plan for SQL Server

When planning to transfer data to SQL Server, you should consider the databases and user information, such as database names, what data is stored, and the database space needed.

Before you begin:

The database names and users in this topic are suggested values and provide consistency throughout the documentation. Replace these values with values in environment.

  1. Review the different databases shown in the following table and replace these values with the values in environment; schema names must be different when the database is shared.

      While configuring WebSphere Portal to use one database is technically possible, using separate databases can improve scalability and performance.

      Application Database name Space required
      WebSphere Portal

      Used for the portal (at a minimum) or to hold all data. Stores information about user customization, such as pages, and user profile and login information.

        reldb

        commdb

        custdb

      		Depends on the number of users and portal objects, such as pages and portlets.
      Personalization,Web Content Manager

      Contains documents, personalization rules, personalization campaigns, and document library configuration information.

        jcrdb
      		Depends on the number and size of Personalization rules and campaigns, and the number and size of items and elements created in Web Content Manager.
      Feedback

      Contains the information that is logged by Web site for analysis of site activity and generating reports.

        fdbkdb
      		Depends on the amount of traffic to the site. The amount of data that is logged per login-enabled page can vary.
      LikeMinds

      Contains the recommendations to be displayed to users when their interactions with Web site have been analyzed and predictions generated.

        lmdb
      		Depends on the amount of traffic to the site.

  2. Connect at least one user to the SQL Server instance.

      A user can be granted permission to use several schema names, so a single user for each instance is sufficient.

  3. Review the tables and types of objects owned by each schema.

      The WebSphere Portal architecture allows each of the following schemata to exist in the same database. All table spaces will be approximately 2.8 GB by default. The size will increase with the use of the Java™ Content Repository function.


      Application


      Database schema placeholder


      Recommended name


      Function
      WebSphere Portal

      • releaseusr
      • communityusr
      • customizationusr

      		<none> Core schemata. Will own approximately 130 tables for each domain. Owns WebSphere Portal core objects, which includes tables that store the user customizations made to Pages.

      Java Content Repository

      icmadmin

      <none>

      Java Content Repository schema. Will own at least 1130 tables; the number could be higher depending on usage.

      Feedback

      feedback

      <none>

      Feedback schema. Will own approximately 50 tables used for logging site and personalization usage.

      Likeminds

      LIKEMINDS

      <none>

      LikeMinds schema. Will own approximately 15 tables used to hold the web site usage analysis routines and recommendation text.


Parent

Database considerations


Related tasks

http://www.ibm.com/support/docview.wss?rs=688&uid=swg27007791

http://www.datadirect.com/products/jdbc/index.ssp

Microsoft SQL Server product documentation

Registry Entries Are Required for XA Transaction Support

http://support.microsoft.com/kb/839279

 


+

Search Tips   |   Advanced Search