Table of Contents

Search

  1. Preface
  2. Data Replication Overview
  3. Understanding Data Replication
  4. Sources - Preparation and Replication Considerations
  5. Targets - Preparation and Replication Considerations
  6. Starting the Server Manager
  7. Getting Started with the Data Replication Console
  8. Defining and Managing Server Manager Main Servers and Subservers
  9. Creating and Managing User Accounts
  10. Creating and Managing Connections
  11. Creating Replication Configurations
  12. Materializing Targets with InitialSync
  13. Scheduling and Running Replication Tasks
  14. Implementing Advanced Replication Topologies
  15. Monitoring Data Replication
  16. Managing Replication Configurations
  17. Handling Replication Environment Changes and Failures
  18. Troubleshooting
  19. Data Replication Files and Subdirectories
  20. Data Replication Runtime Parameters
  21. Command Line Parameters for Data Replication Components
  22. Updating Configurations in the Replication Configuration CLI
  23. DDL Statements for Manually Creating Recovery Tables
  24. Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Glossary

Preparing Microsoft SQL Server Source Systems

Preparing Microsoft SQL Server Source Systems

After you install Informatica Data Replication on a Microsoft SQL Server source system, you must complete several tasks to prepare the system for data replication.
  1. On Windows, download and install .NET Framework 3.5 SP1 or later from the Microsoft web site if it is not currently installed.
  2. Verify that the Microsoft SQL Server database uses Mixed Mode Authentication to allow use of SQL Server Authentication.
  3. Create an SQL Server login account that uses SQL Server Authentication. Use SQL Server Management Studio or the following Transact-SQL statement:
    CREATE LOGIN
    datarep_user
    WITH PASSWORD = '
    password
    '; GO
  4. Create a user in the master database and grant the permissions that Data Replication requires to this user. Use the following SQL statements:
    use [master] CREATE USER
    datarep_user
    FOR LOGIN
    datarep_user
    ; GRANT VIEW SERVER STATE TO
    datarep_user
    ; GRANT VIEW ANY DEFINITION TO
    datarep_user
    ; GRANT SELECT TO
    datarep_user
    ; GO
  5. Create a user for each source database and assign the db_owner role to this user. Use the following SQL statements:
    use [
    source_mssql_database_name
    ] CREATE USER
    datarep_user
    FOR LOGIN
    datarep_user
    ; EXEC sp_addrolemember 'db_owner', '
    datarep_user
    ' GO
    Data Replication requires the db_owner role to perform the following tasks:
    • To connect to Microsoft SQL Server sources from the Data Replication Console
    • To create backup logs for Microsoft SQL Server sources with the Server Manager
    • To enable Change Data Capture for a replication job
    Data Replication also requires the "public" server role, to which every database user belongs by default.
  6. To use the Server Manager to create backup logs in SQL Server native format, assign the db_backupoperator role to the user in each source database. Use the following SQL statements:
    use [
    source_mssql_database_name
    ] EXEC sp_addrolemember 'db_backupoperator', '
    datarep_user
    ' GO
    Data Replication can capture change data from backup logs in SQL Server native format.
  7. If you plan to run the Server Manager on a computer that is remote from the SQL Server source, set the
    remote admin connections
    option of the SQL Server sp_configure stored procedure to 1. Use the following commands:
    sp_configure 'remote admin connections', 1; GO RECONFIGURE; GO
    This setting enables the remote Server Manager to use a dedicated administrator connection (DAC) to the SQL Server source.
  8. Optionally, if you capture data from online transaction logs, assign the sysadmin role to the user for each source database to enhance performance. You can run the following stored procedure:
    use [
    source_mssql_database_name
    ] EXEC sp_addsrvrolemember @loginame= '
    datarep_user
    ', @rolename = 'sysadmin' GO
    The Extractor task uses one of the following methods to get the list of active virtual log files (VLFs) from the Microsoft SQL Server source:
    • If the user has the sysadmin role, the Extractor uses the DBCC LOGINFO command to get the information about the VLFs in the transaction log. This method is faster.
    • If the user does not have the sysadmin role, the Extractor scans transaction logs and processes VLF headers to get the information about the VLFs in the transaction log without running the DBCC LOGINFO command. This method is slower.
  9. Ensure that all databases from which data will be extracted are set to the Full Recovery Model.
  10. Create a full backup of each database from which data will be extracted.
  11. Enable snapshot isolation for all of the SQL Server source databases to correctly replicate changes that might occur during InitialSync initial synchronization of the target tables with the SQL Server source tables. Use the following syntax to run the ALLOW_SNAPSHOT_ISOLATION statement for each of the source databases:
    ALTER DATABASE
    source_mssql_database_name
    SET ALLOW_SNAPSHOT_ISOLATION ON;
    You can skip this step if you do not use InitialSync for initial synchronization of the source and target tables.
  12. In Microsoft SQL Server Configuration Manager, under Network Configuration, enable TCP/IP as the protocol for the SQL Server instance.
  13. For Microsoft SQL Server 64-bit software, add
    DBSYNC_HOME\support
    to the PATH environment variable.
  14. If you plan to capture data from compressed backup transaction logs, ensure that the system account under which the Extractor runs has write permissions on the directory that contains the compressed log files.

0 COMMENTS

We’d like to hear from you!