Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Row count mismatch Between Cloud and Backup table

Row counts mismatches between SF cloud and the SF backup.

TAbleName Total Rows
Event_cloud 78054
Event_backup 88236
1 person has
this question
+1
Reply
  • What DBAmp command did you run for the backup? Can you post the complete message output from that command? Also, what version of DBAmp are you currently running?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • DBAmp version: 3.4.8.0
    This is the command we use to run for the refresh
    exec sf_refresh 'SALESFORCE', 'Event', 'yes'

    Output of the refresh job:
    --- Starting SF_Refresh for User V3.4.7
    22:16:44: Using Schema Error Action of yes
    22:16:45: Using last run time of 2017-11-29 03:30:00
    22:16:50: Identified 444 updated/inserted rows.
    22:16:50: Identified 0 deleted rows.
    22:16:50: Adding updated/inserted rows into User
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for UserRole V3.4.7
    22:16:50: Using Schema Error Action of yes
    22:16:51: Using last run time of 2017-11-29 03:30:00
    22:16:51: Identified 1 updated/inserted rows.
    22:16:51: Identified 0 deleted rows.
    22:16:51: Adding updated/inserted rows into UserRole
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Account V3.4.7
    22:16:51: Using Schema Error Action of yes
    22:16:52: Using last run time of 2017-11-29 14:46:00
    22:17:12: Identified 2410 updated/inserted rows.
    22:17:12: Identified 4 deleted rows.
    22:17:12: Removing deleted rows from Account
    22:17:12: Adding updated/inserted rows into Account
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Contact V3.4.7
    22:17:14: Using Schema Error Action of yes
    22:17:15: Using last run time of 2017-11-29 03:30:00
    22:17:53: Identified 4859 updated/inserted rows.
    22:17:53: Identified 16 deleted rows.
    22:17:53: Removing deleted rows from Contact
    22:17:53: Adding updated/inserted rows into Contact
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Case V3.4.7
    22:17:55: Using Schema Error Action of yes
    22:17:56: Using last run time of 2017-11-29 03:30:00
    22:18:15: Identified 2564 updated/inserted rows.
    22:18:15: Identified 17 deleted rows.
    22:18:15: Removing deleted rows from Case
    22:18:15: Adding updated/inserted rows into Case
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Opportunity V3.4.7
    22:18:21: Using Schema Error Action of yes
    22:18:22: Using last run time of 2017-11-29 03:30:00
    22:18:30: Identified 950 updated/inserted rows.
    22:18:30: Identified 1 deleted rows.
    22:18:30: Removing deleted rows from Opportunity
    22:18:30: Adding updated/inserted rows into Opportunity
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for OpportunityHistory V3.4.7
    22:18:31: Using Schema Error Action of yes
    22:18:31: Using last run time of 2017-11-29 03:30:00
    22:18:32: Identified 720 updated/inserted rows.
    22:18:32: Identified 3 deleted rows.
    22:18:32: Removing deleted rows from OpportunityHistory
    22:18:32: Adding updated/inserted rows into OpportunityHistory
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for OpportunityLineItem V3.4.7
    22:18:32: Using Schema Error Action of yes
    22:18:33: Using last run time of 2017-11-29 03:30:00
    22:18:34: Identified 256 updated/inserted rows.
    22:18:34: Identified 4 deleted rows.
    22:18:34: Removing deleted rows from OpportunityLineItem
    22:18:34: Adding updated/inserted rows into OpportunityLineItem
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for RecordType V3.4.7
    22:18:34: Using Schema Error Action of yes
    22:18:34: Using last run time of 2017-11-29 03:30:00
    22:18:35: Identified 0 updated/inserted rows.
    22:18:35: Identified 0 deleted rows.
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for AccountHistory V3.4.7
    22:18:35: Using Schema Error Action of yes
    22:18:35: Using last run time of 2017-11-29 03:30:00
    22:18:36: Identified 556 updated/inserted rows.
    22:18:37: Identified 22 deleted rows.
    22:18:37: Removing deleted rows from AccountHistory
    22:18:37: Adding updated/inserted rows into AccountHistory
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for ContactHistory V3.4.7
    22:18:37: Using Schema Error Action of yes
    22:18:37: Using last run time of 2017-11-29 03:30:00
    22:18:38: Identified 1436 updated/inserted rows.
    22:18:39: Identified 116 deleted rows.
    22:18:39: Removing deleted rows from ContactHistory
    22:18:39: Adding updated/inserted rows into ContactHistory
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for CaseHistory V3.4.7
    22:18:39: Using Schema Error Action of yes
    22:18:39: Using last run time of 2017-11-29 03:30:00
    22:18:42: Identified 5670 updated/inserted rows.
    22:18:42: Identified 51 deleted rows.
    22:18:42: Removing deleted rows from CaseHistory
    22:18:42: Adding updated/inserted rows into CaseHistory
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for emailMessage V3.4.7
    22:18:43: Using Schema Error Action of yes
    22:18:43: Using last run time of 2017-11-29 03:31:00
    22:19:00: Identified 1144 updated/inserted rows.
    22:19:00: Identified 26 deleted rows.
    22:19:00: Removing deleted rows from emailMessage
    22:19:00: Adding updated/inserted rows into emailMessage
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for External_Contact__c V3.4.7
    22:19:07: Using Schema Error Action of yes
    22:19:08: Using last run time of 2017-11-29 03:31:00
    22:19:08: Identified 313 updated/inserted rows.
    22:19:08: Identified 2 deleted rows.
    22:19:08: Removing deleted rows from External_Contact__c
    22:19:09: Adding updated/inserted rows into External_Contact__c
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Event V3.4.7
    22:19:09: Using Schema Error Action of yes
    22:19:09: Using last run time of 2017-11-29 16:54:00
    22:19:09: Identified 84 updated/inserted rows.
    22:19:10: Identified 0 deleted rows.
    22:19:10: Adding updated/inserted rows into Event
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for task V3.4.7
    22:19:10: Using Schema Error Action of yes
    22:19:10: Using last run time of 2017-11-29 03:31:00
    22:19:16: Identified 2049 updated/inserted rows.
    22:19:16: Identified 8 deleted rows.
    22:19:16: Removing deleted rows from task
    22:19:16: Adding updated/inserted rows into task
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Campaign V3.4.7
    22:19:18: Using Schema Error Action of yes
    22:19:19: Using last run time of 2017-11-29 03:31:00
    22:19:19: Identified 40 updated/inserted rows.
    22:19:19: Identified 0 deleted rows.
    22:19:19: Adding updated/inserted rows into Campaign
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for CampaignMember V3.4.7
    22:19:19: Using Schema Error Action of yes
    22:19:20: Using last run time of 2017-11-29 14:46:00
    22:19:20: Identified 11 updated/inserted rows.
    22:19:20: Identified 0 deleted rows.
    22:19:20: Adding updated/inserted rows into CampaignMember
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for AccountContactRole V3.4.7
    22:19:20: Using Schema Error Action of yes
    22:19:20: Using last run time of 2017-11-29 03:31:00
    22:19:21: Identified 0 updated/inserted rows.
    22:19:21: Identified 0 deleted rows.
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for product2 V3.4.7
    22:19:21: Using Schema Error Action of yes
    22:19:21: Using last run time of 2017-11-29 16:21:00
    22:19:21: Identified 41 updated/inserted rows.
    22:19:22: Identified 0 deleted rows.
    22:19:22: Adding updated/inserted rows into product2
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Cmp_territory__c V3.4.7
    22:19:22: Using Schema Error Action of yes
    22:19:22: Using last run time of 2017-11-29 03:31:00
    22:19:22: Identified 27 updated/inserted rows.
    22:19:23: Identified 0 deleted rows.
    22:19:23: Adding updated/inserted rows into Cmp_territory__c
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for OpportunityFieldHistory V3.4.7
    22:19:23: Using Schema Error Action of yes
    22:19:23: Using last run time of 2017-11-29 03:31:00
    22:19:24: Identified 1862 updated/inserted rows.
    22:19:25: Identified 27 deleted rows.
    22:19:25: Removing deleted rows from OpportunityFieldHistory
    22:19:25: Adding updated/inserted rows into OpportunityFieldHistory
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Note V3.4.7
    22:19:25: Using Schema Error Action of yes
    22:19:25: Using last run time of 2017-11-29 03:31:00
    22:19:25: Identified 27 updated/inserted rows.
    22:19:26: Identified 6 deleted rows.
    22:19:26: Removing deleted rows from Note
    22:19:26: Adding updated/inserted rows into Note
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Asset V3.4.7
    22:19:26: Using Schema Error Action of yes
    22:19:26: Using last run time of 2017-11-29 03:31:00
    22:19:40: Identified 7163 updated/inserted rows.
    22:19:41: Identified 30 deleted rows.
    22:19:41: Removing deleted rows from Asset
    22:19:41: Adding updated/inserted rows into Asset
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Folder V3.4.7
    22:19:41: Using Schema Error Action of yes
    22:19:42: Using last run time of 2017-11-29 03:31:00
    22:19:42: Identified 0 updated/inserted rows.
    22:19:42: Identified 0 deleted rows.
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for ForecastShare V3.4.7
    22:19:42: Using Schema Error Action of yes
    22:19:42: Table does not contain a timestamp column needed to refresh. Using SF_Replicate to create table.
    --- Starting SF_Replicate for ForecastShare V3.4.7
    22:19:42: Parameters: SALESFORCE ForecastShare Version: V3.4.7
    22:19:42: Drop ForecastShare_Previous if it exists.
    22:19:42: Create ForecastShare_Previous with new structure.
    22:19:44: DBAmpNet2 3.4.8.0 (c) Copyright 2015-2017 forceAmp.com LLC
    22:19:45: Parameters: exportsoap ForecastShare_Previous APVTHAU23046 salesforce_backups SALESFORCE
    22:19:51: 12 rows copied.
    22:19:51: DBAmpNet2 Operation successful.
    22:19:51: Drop ForecastShare if it exists.
    22:19:51: Rename previous table from ForecastShare_Previous to ForecastShare
    Caution: Changing any part of an object name could break scripts and stored procedures.
    22:19:52: Create primary key on ForecastShare
    --- Ending SF_Replicate. Operation successful.
    --- Starting SF_Refresh for ForecastingAdjustment V3.4.7
    22:19:52: Using Schema Error Action of yes
    22:19:52: Using last run time of 2017-11-29 03:31:00
    22:19:52: Identified 0 updated/inserted rows.
    22:19:52: Identified 0 deleted rows.
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for ForecastingCategoryMapping V3.4.7
    22:19:52: Using Schema Error Action of yes
    22:19:53: Using last run time of 2017-11-29 03:31:00
    22:19:53: Identified 0 updated/inserted rows.
    22:19:53: Using alternate method to determine deleted records.
    22:19:53: Identified 0 deleted rows.
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for ForecastingItem V3.4.7
    22:19:53: Using Schema Error Action of yes
    22:19:53: Using last run time of 2017-11-29 03:31:00
    22:19:54: Identified 150 updated/inserted rows.
    22:19:54: Using alternate method to determine deleted records.
    22:19:59: Identified 0 deleted rows.
    22:19:59: Adding updated/inserted rows into ForecastingItem
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for ForecastingOwnerAdjustment V3.4.7
    22:19:59: Using Schema Error Action of yes
    22:19:59: Using last run time of 2017-11-29 03:31:00
    22:20:00: Identified 0 updated/inserted rows.
    22:20:00: Identified 0 deleted rows.
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for ForecastingQuota V3.4.7
    22:20:00: Using Schema Error Action of yes
    22:20:00: Using last run time of 2017-11-29 03:31:00
    22:20:00: Identified 0 updated/inserted rows.
    22:20:00: Identified 0 deleted rows.
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for ForecastingType V3.4.7
    22:20:00: Using Schema Error Action of yes
    22:20:01: Using last run time of 2017-11-29 03:31:00
    22:20:01: Identified 0 updated/inserted rows.
    22:20:01: Using alternate method to determine deleted records.
    22:20:01: Identified 0 deleted rows.
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for ForecastingTypeToCategory V3.4.7
    22:20:01: Using Schema Error Action of yes
    22:20:01: Using last run time of 2017-11-29 03:31:00
    22:20:02: Identified 0 updated/inserted rows.
    22:20:02: Using alternate method to determine deleted records.
    22:20:02: Identified 0 deleted rows.
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Customer_Groups__c V3.4.7
    22:20:02: Using Schema Error Action of yes
    22:20:02: Using last run time of 2017-11-29 03:31:00
    22:20:04: Identified 964 updated/inserted rows.
    22:20:04: Identified 0 deleted rows.
    22:20:04: Adding updated/inserted rows into Customer_Groups__c
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Customer_Group_Members__c V3.4.7
    22:20:04: Using Schema Error Action of yes
    22:20:04: Using last run time of 2017-11-29 03:31:00
    22:20:15: Identified 19240 updated/inserted rows.
    22:20:15: Identified 198 deleted rows.
    22:20:15: Removing deleted rows from Customer_Group_Members__c
    22:20:15: Adding updated/inserted rows into Customer_Group_Members__c
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Group_Product__c V3.4.7
    22:20:16: Using Schema Error Action of yes
    22:20:17: Using last run time of 2017-11-29 03:31:00
    22:20:18: Identified 768 updated/inserted rows.
    22:20:18: Identified 0 deleted rows.
    22:20:18: Adding updated/inserted rows into Group_Product__c
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for mo_User_Detail__c V3.4.7
    22:20:18: Using Schema Error Action of yes
    22:20:18: Using last run time of 2017-11-29 03:31:00
    22:20:19: Identified 400 updated/inserted rows.
    22:20:19: Identified 0 deleted rows.
    22:20:19: Adding updated/inserted rows into mo_User_Detail__c
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for Order V3.4.7
    22:20:19: Using Schema Error Action of yes
    22:20:20: Using last run time of 2017-11-29 16:24:00
    22:20:20: Identified 79 updated/inserted rows.
    22:20:20: Identified 0 deleted rows.
    22:20:20: Adding updated/inserted rows into Order
    --- Ending SF_Refresh. Operation successful.
    --- Starting SF_Refresh for obj_Order_Tracking__c V3.4.7
    22:20:21: Using Schema Error Action of yes
    22:20:21: Using last run time of 2017-11-29 03:31:00
    22:20:21: Identified 225 updated/inserted rows.
    22:20:22: Identified 0 deleted rows.
    22:20:22: Adding updated/inserted rows into obj_Order_Tracking__c
    --- Ending SF_Refresh. Operation successful.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited

  • Were there a bunch of events deleted recently up on Salesforce? If you run the following command, do the counts sync back up:

    exec SF_Replicate 'SALESFORCE', 'Event'
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited

  • Sorry the command is just one table we run in the refresh job . The output is from actual daily refresh job for multiple tables
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited

  • Try the following in a new query window:

    exec SF_Replicate 'SALESFORCE', 'Event'

    Do they sync back up?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Current Status after replicate:
    TNAME Row Count
    ---------- ----------
    Event_cloud 78721
    Event_backup 78718

    Before the replicate of Event table, the count was showing high but after replication the count nearly matched. Not sure why refresh command did not sync up the backup correctly.

    --- Starting SF_Replicate for Event V3.4.7
    15:23:52: Parameters: SALESFORCE Event Version: V3.4.7
    15:23:52: Drop Event_Previous if it exists.
    15:23:52: Create Event_Previous with new structure.
    15:23:55: DBAmpNet2 3.4.8.0 (c) Copyright 2015-2017 forceAmp.com LLC
    15:23:55: Parameters: exportsoap Event_Previous APVTHAU23046 salesforce_backups SALESFORCE
    15:25:08: 78718 rows copied.
    15:25:08: DBAmpNet2 Operation successful.
    15:25:08: Drop Event if it exists.
    15:25:08: Rename previous table from Event_Previous to Event
    Caution: Changing any part of an object name could break scripts and stored procedures.
    15:25:08: Create primary key on Event
    --- Ending SF_Replicate. Operation successful.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • If you see it getting out of sync again, let us know and we can take a closer look at it.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited

  • After replicating the Event table, again I see the difference in count for 'Event' table around 1500 records though refresh runs daily.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • How often are you running SF_Refresh on the Event table? Are there a lot of Event records being created or deleted all the time on Salesforce?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Refresh runs daily and yes it seems like lot of records being inserted deleted in Salesforce.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Well if you only run it once a day, then the changes only get picked up once a day. If you say there are a lot of records being inserted and deleted in Salesforce, then until the Refresh runs again the counts will mismatch.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • The scheduled refresh runs once a day, but I also did manual refresh of table and checked the count immediately and still not synced
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited

  • Where are you getting the Cloud number from? How much were they off after you ran it manually?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited

  • Using this query from local to get the count from cloud.

    Select count(*) FROM [SALESFORCE]...[Event]

    More than 1000 records was high on backup since the table was just replicated during last sunday. And even after doing refresh manually to check the count sync, it was not synced.

    on Cloud: 78332
    on Backup: 79861
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited

  • If you do a manual refresh of the Event table right now, then do a count of the local table and a count of the Salesforce...Event table, what are the counts?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Also, can you post the complete message output from the manual refresh you run?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited

  • Since recently replicated Event table the backup count is syncing with cloud.
    But the question is, it is getting synced properly only on Replication, not properly syncing with Refresh command as there were huge count difference in backup table.
    I will monitor another couple of days

    Before Refresh:
    Cloud Event: 78512
    Backup Event: 78365

    --- Starting SF_Refresh for Event V3.4.7
    17:36:37: Using Schema Error Action of yes
    17:36:39: Using last run time of 2017-12-06 03:31:00
    17:36:40: Identified 308 updated/inserted rows.
    17:36:41: Identified 2 deleted rows.
    17:36:41: Removing deleted rows from Event
    17:36:41: Adding updated/inserted rows into Event
    --- Ending SF_Refresh. Operation successful.

    After Refresh:
    Cloud Event: 78513
    Backup Event: 78513
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • I see the significant count difference today, so I did run the refresh and checked the count and still the same difference.

    exec sf_refresh 'SALESFORCE', 'Event','yes'

    --- Starting SF_Refresh for Event V3.4.7
    03:03:16: Using Schema Error Action of yes
    03:03:18: Using last run time of 2017-12-11 23:09:00
    03:03:19: Identified 0 updated/inserted rows.
    03:03:19: Identified 0 deleted rows.
    --- Ending SF_Refresh. Operation successful.

    FunctionName DateTimeFormat
    ------------ --------------
    SYSDATETIME 2017-12-12 03:03:49.4389608

    TNAME Counts
    ----------- ------
    Event_cloud 77820
    Event_backup 79017
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited

  • Lets say on Friday there are 5 event records, you do a refresh and the counts match. Then let's say on Saturday, Salesforce archives 2 of those 5 event records (this is not the same as delete). The Salesforce API is unaware of records that are archived. So, on Monday when you do another refresh, it will report 0 updated/inserted rows and 0 deleted rows. But, if you ask Salesforce for a count of the number of records in the Event table, then the value will be 3, even though the local table has 5.

    So, if you want to account for archived records, you must use the IAD versions of both replicate and refresh. Archiving only occurs on the Task and Event objects in Salesforce.

    For more information on Archived Events, take a look at the following link: https://help.salesforce.com/articleVi...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited