Creating databases or schemas

Set up data sources so that the Opportunity Detect system can store user and interaction data. Use Campaign Customer (user) tables or set up unique data sources based on the type of data that is stored.

About this task

Complete the following steps to create databases or schemas for Opportunity Detect.

Procedure

  1. Create a database or a database schema for the Opportunity Detect system tables.
    The following table provides information about vendor-specific guidelines for creating a database or a database schema for the Opportunity Detect system tables.
    Note: If you are using multiple databases, for example for profile and lookup data and system tables, they must all be of the same supported type: DB2 or Oracle.
    Table 1. Guidelines for creating databases or schemas

    This two-columned table provides information about the database vendor in one column, and the guidelines that must be followed while you create the database or schema in the second column.
    Database vendor Guidelines
    Oracle Enable the auto commit feature for the environment open. See the Oracle documentation for instructions.
    DB2® Set the database page size to at least 16K, or 32K if you need to support Unicode. See the DB2 documentation for instructions.
    SQL Server Use either the SQL Server authentication, or both the SQL Server and Windows™ authentication, because Marketing Platform requires SQL Server authentication. If necessary, change the database configuration so that your database authentication includes SQL Server. Also, be sure that TCP/IP is enabled in your SQL Server.
    Note: If you plan to enable locales that use multi-byte characters, such as Chinese, Korean, and Japanese, ensure that the database is created to support them.
    Note: When you create your databases, you should use the same code page for all of your databases. You cannot change this code page once it is set. If you did not create your databases to use the same code page, you must use only the characters supported in the code page. For example, if you create a zone in global offers that does not use a character in the profile database code page, the global offer does not work.
    Note: Database names in Interact must follow the naming convention for ordinary identifiers (also known as "non-quoted identifiers or regular identifiers) for the brand of SQL used (DB2, Oracle, SQL Server, and so on). Refer to your database provider documentation for specific details. Typically, alphabetic letters, numbers, and underscores are allowed by all flavors of SQL. Hyphens and other characters not permitted in ordinary identifiers will likely cause SQL exceptions.
  2. Create a database user account.

    The account that you create must have at least CREATE, SELECT, INSERT, UPDATE, DELETE, and DROP rights.

  3. Obtain information about your databases or schemas and database accounts and then print and add the information to the Opportunity Detect installation worksheet. You can use this information later in the installation process.
  4. Obtain information about your databases or schemas and database accounts and then print and add the information to the Opportunity Detect installation worksheet. You can use this information later in the installation process.