Table of Contents

Search

  1. Preface
  2. Starting Data Archive
  3. System Configuration
  4. Database Users and Privileges
  5. Source Connections
  6. Target Connections
  7. Archive Store Configuration
  8. Datatype Mapping
  9. Database Optimization
  10. SAP Application Retirement
  11. z/OS Source Data Retirement
  12. Seamless Data Access
  13. Data Discovery Portal
  14. Security
  15. SSL Communication with Data Vault
  16. LDAP User Authentication
  17. Auditing
  18. Running Jobs from External Applications
  19. Salesforce Archiving Administrator Tasks
  20. Upgrading Oracle History Data
  21. Upgrading PeopleSoft History Data
  22. Data Archive Maintenance
  23. Appendix A: Datetime and Numeric Formatting
  24. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

Microsoft SQL Server Target Connections

Microsoft SQL Server Target Connections

When you define an archive target connection for Microsoft SQL Server databases, you can choose from multiple connection types. The connection type you choose depends on the database version.
Choose one of the following connection types to connect to a Microsoft SQL Server database:
  • Microsoft SQL Server 2000
  • Microsoft SQL Server 2005
  • Microsoft SQL Server 2008
  • Microsoft SQL Server 2012
  • Microsoft SQL Server 2014
  • Microsoft SQL Server 2016
  • Microsoft SQL Server 2017
The properties that you configure depend on the connection type that you choose. Some properties are not relevant for all connection types. Property names may vary between connection types.
Depending on the connection type, you can configure the following target connection properties:
Host
Host of the target application database server.
Port
Port of the target application database server.
Admin Database
Default administration database for the target database server. Default is master.
Admin Database Owner
Administration database owner that has DBA rights to the database, including the ability to execute DDL and access system-level objects.
Default is dbo.
Admin Login Name
Login name for the administration database server. This user does not require special permissions as it is only used to connect to the target database. You can provide any user name, such as a database connection user or a read-only user.
Password
Password for the administration login name.
Application Database
Database that contains the application tables that you want to archive to.
Apps Database Owner
Application database owner that owns the application tables you want to archive to. Default is dbo.
Application Login Name
Login name for the target application database user.
Password
Password for the application login name.
Data Filegroup
Tablespace name in the application database user that stores the history tables when you run an archive cycle. The archive job always stores the history tables in this tablespace. The archive job only stores staging tables in this tablespace if you configure the source to use staging.
Index Filegroup
Index tablespace name for the history tables.
Database Link to Source or Linked Server Name to Source
Database link name that connects the target database to the source database. The archive job uses the database link when the job copies data to the destination.
If you do not provide a value, then the archive job uses JDBC to move the data.
Drop Destination Indexes
Controls whether the archive job drops the index on the history database before it inserts data in the history database. Use to improve performance when the archive job copies data to the destination.
Disable Triggers
Determines whether the system disables insert, update, and delete triggers when the archive job deletes rows from tables.
If enabled, the system disables triggers when the archive job deletes data from the source.
If disabled, the system retains the triggers.
Default is enabled.
Only valid for restore archive jobs.
Target Attachment Location
Required to restore archived attachments from the history database or from the Data Vault to the source database.
Enter the target directory where you want to restore the external attachments. The directory is the location where the source application reads the attachments from. You must have write access to the directory.
Source/Staging Attachment Location
Required to restore archived attachments from the history database or from the Data Vault to the source database. The definition depends on the archived attachment location and whether the attachments are encrypted.
To restore attachments from the history database and non-encrypted attachments from the Data Vault, enter the current location of the archived attachments. This is the location where you originally archived the attachments to. You must have read access to the directory.
To restore encrypted attachments, such as Siebel attachments, from the Data Vault, enter a temporary location that is accessible to the ILM engine and the Data Vault Service for External Attachments component. The restore job moves the attachments from the Data Vault Service AM_ATTACHMENTS table to this temporary location.
Staging Script Location
Required to restore archived attachments from the history database or from the Data Vault to the source database. Enter a temporary location to store the script that the restore job generates.
For attachments in the history database and non-encrypted attachments from the Data Vault, the script moves the attachments from the source attachment location to the target attachment location.
For encrypted attachments in the Data Vault, the script uses the source application encryption utility to encrypt the attachments back into the source application proprietary format. Then, the script moves the attachments from the staging attachment location to the target attachment location.
Add-On URL
Required to restore encrypted attachments from the Data Vault to the source database. Enter the URL for the Data Vault Service for External Attachments. The Data Vault Service for External Attachments converts external attachments from the archived format into the source proprietary format.
Available for Microsoft SQL Server 2005 and Microsoft SQL Server 2008.

0 COMMENTS

We’d like to hear from you!