Usage

SF_ReplicateAll creates a full backup of your Salesforce.com data as replicated tables in the remote database of the remote SQL Server Instance with the contents of the same object at Salesforce.com. Any schema changes in the object at Salesforce.com are reflected in the new table.

However, Salesforce objects that cannot be queried directly via the Salesforce API (like ActivityHistory) are not included. SF_ReplicateAll also skips Chatter Feed objects because of the excessive API calls required to download those objects. You can modify the stored procedures to include them if needed.

Syntax

EXEC SF_replicateall '𝘭𝘪𝘯𝘬𝘦𝘥_𝘴𝘦𝘳𝘷𝘦𝘳', 'allow_fail', 'error_messages_only', 'use_remote'

where linked_server is your linked server name. use_remote must be set to 1.

ExampleleOptions Table

Use the DBAmpTableO

The following example replicates all the current data on Salesforce.com using the SALESFORCE linked server.

EXEC SF_replicateall 'SALESFORCE', 'no', 'no', 1

Using the DBAmpTabptions table to skip tables that are not needed in the remote database. In addition, use the DBAmpTableOptions table to provide replicate options for tables. You can specify options to tell SF_ReplicateAll how to replicate the table locally. See “Using the DBAmpTableOptions Table” for more information.

Notes

• SF_ReplicateAll calls SF_Replicate for each Salesforce.com object. • There are some tables, like Vote and UserProfileFeed, in Salesforce that are not included in SF_ReplicateAll. The Salesforce.com API does not allow selecting all rows from these tables. SF_ReplicateAll also skips Chatter Feed objects because of the excessive API calls required to download those objects. You can modify the stored procedures to include them if needed. • By default, DBAmp does not download the values of Base64 fields but instead sets the value to NULL. This is done for performance reasons. If you require the actual values, change the Include Binary Field Valuessetting to True in the Settings page of the DBAmp Configuration program.