Skip to main content
ss_DeltaAll
Updated over 8 months ago

ss_DeltaAll allows you to run ss_Delta in bulk.

Simple Example

exec ss_DeltaAll 'DEMO'

With @ObjectNameFrom

exec ss_DeltaAll 'DEMO', 'Opportunity'

This will commence the bulk ss_Delta replication from the Object immediately following Opportunity, which could be OpportunityCompetitor if there is no other custom or standard object with a name closer to Opportunity, sorting alphabetically. This is useful if a prior run of ss_DeltaAll has failed for whatever reason and you wish to re-commence from the point of failure.

With AutoReplica = Yes

exec ss_DeltaAll 'DEMO',null,’Yes’

@AutoReplica will be passed through to each attempted ss_Delta, which will automatically failover to ss_Replica should any AutoReplica condition be met.

Parameters

Parameter

Purpose

@Env

SQL Sales Environment Name

@ObjectNameFrom

This will commence the bulk ss_Delta replication from the Object immediately following the one passed in via @ObjectNameFrom. This is useful if a prior run of ss_DeltaAll has failed for whatever reason and you wish to re-commence from the point of failure.

@AutoReplica

@AutoReplica will be passed through to each attempted ss_Delta, which will automatically failover to ss_Replica should any AutoReplica condition be met.

ss_ObjectInclusion inclusion table

Field

Purpose

ObjectName

Definition of Objects you wish to include in each ss_DeltaAll run. Only Objects contained in this table will be considered in scope. Accompanying table ss_ObjectExclusion will additionally be referenced, i.e. Objects within will be ignored.

ss_ObjectInclusion exclusion table

Field

Purpose

ObjectName

Add any Objects in this table to have them excluded from each ss_DeltaAll run. On deployment (ss_EnableDatabase) a number of known problem Objects are included in this table along with their API Response Error Msg and Codes, for general reference.

It is a matter of choice whether you specify an Inclusion set (via ss_ObjectInclusion) or exclude via this table. Generally, only a relatively small number of Salesforce objects are required to maintain a working replication database and hence ss_ObjectInclusion is more appropriate, or even a hard coded list of ss_Delta commands for each required Object, for example:

ss_Delta ‘DEMO’, ‘Account’

ss_Delta ‘DEMO’, ‘AccountHistory’

ss_Delta ‘DEMO’, ‘Opportunity’

Which is run via a SQL Agent Job or similar.

Running with no entries in this table but some entries in ss_ObjectExclusion would be more appropriate, if you wanted to automatically take an entire backup of your Salesforce Org, for example.

ErrorMsg

Salesforce API Response Error Msg

ErrorCode

Salesforce API Response Error code


Did this answer your question?