Create a Microsoft SQL Server Model

7-6 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator

7.5.2 Reverse-engineer a Microsoft SQL Server Model

Microsoft SQL Server supports both Standard reverse-engineering - which uses only the abilities of the JDBC driver - and Customized reverse-engineering, which uses a RKM to retrieve the metadata. In most of the cases, consider using the standard JDBC reverse engineering for starting. Standard reverse-engineering with Microsoft SQL Server retrieves tables, views, and columns. Consider switching to customized reverse-engineering for retrieving more metadata. Microsoft SQL Server customized reverse-engineering retrieves the tables, views, and synonyms. The RKM MSSQL also reverse-engineers columns that have a user defined data type and translates the user defined data type to the native data type. Standard Reverse-Engineering To perform a Standard Reverse-Engineering on Microsoft SQL Server use the usual procedure, as described in Reverse-engineering a Model of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. Customized Reverse-Engineering To perform a Customized Reverse-Engineering on Microsoft SQL Server with a RKM, use the usual procedure, as described in Reverse-engineering a Model of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. This section details only the fields specific to the Microsoft SQL Server technology: 1. In the Reverse tab of the Microsoft SQL Server Model, select the KM: RKM MSSQL.project name. 2. In the COMPATIBLE option, enter the Microsoft SQL Server version. This option decides whether to enable reverse synonyms. Note that only Microsoft SQLServer version 2005 and above support synonyms. Note the following information when using this RKM: ■ The connection user must have SELECT privileges on any INFORMATION_ SCHEMA views. ■ Only native data type will be saved for the column with user defined data type in the repository and model. ■ User defined data types implemented through a class of assembly in the Microsoft .NET Framework common language runtime CLR will not be reversed.

7.6 Setting up Changed Data Capture

The ODI Microsoft SQL Server Knowledge Modules support the Changed Data Capture feature. See Chapter Working with Changed Data Capture of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator for details on how to set up journalizing and how to use captured changes. Microsoft SQL Server Journalizing Knowledge Modules support Simple Journalizing and Consistent Set Journalizing. The Microsoft SQL Server JKMs use triggers to capture data changes on the source tables. Oracle Data Integrator provides the Knowledge Modules listed in Table 7–2 for journalizing Microsoft SQL Server tables. Microsoft SQL Server 7-7 Log-based changed data capture is possible with Microsoft SQL Server using the Oracle Changed Data Capture Adapters. See Chapter 28, Oracle Changed Data Capture Adapters for more information.

7.7 Setting up Data Quality

Oracle Data Integrator provides the generic CKM SQL for checking data integrity against constraints defined on a Microsoft SQL Server table. See Set up Flow Control and Post-Integration Control in the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator for details. See Chapter 4, Generic SQL for more information.

7.8 Designing an Interface

You can use Microsoft SQL Server as a source, staging area or a target of an integration interface. The KM choice for an interface or a check determines the abilities and performance of this interface or check. The recommendations in this section help in the selection of the KM for different situations concerning a Microsoft SQL Server data server.

7.8.1 Loading Data from and to Microsoft SQL Server

Microsoft SQL Server can be used as a source, target or staging area of an interface. The LKM choice in the Interface Flow tab to load data between Microsoft SQL Server and another type of data server is essential for the performance of an interface.

7.8.1.1 Loading Data from Microsoft SQL Server

Oracle Data Integrator provides Knowledge Modules that implement optimized methods for loading data from Microsoft SQL Server to a target or staging area database. These optimized Microsoft SQL Server KMs are listed in Table 7–3 . In addition to these KMs, you can also use the Generic SQL KMs or the KMs specific to the other technology involved to load data from Microsoft SQL Server to a target or staging area database. Table 7–2 Microsoft SQL Server Journalizing Knowledge Modules KM Notes JKM MSSQL Consistent Creates the journalizing infrastructure for consistent journalizing on Microsoft SQL Server tables using triggers. JKM MSSQL Simple Creates the journalizing infrastructure for simple journalizing on Microsoft SQL Server tables using triggers.