DBAmp SQL Server Integration

Issue: Review video for troubleshooting content
Cause: Document root causes
Resolution: Document solutions
Timestamp: Add timestamp link

VIDEO TRANSCRIPT | Recorded: 2025-12-17 | Verify against current system state

Abstract¶

DBAmp configuration and usage for SQL Server to Salesforce integration, including linked server setup and data synchronization

This article was auto-generated from the video transcript. Review and enhance the content based on the full video.

Use SF_Mirror command for data synchronization (preferred method over SF_Replicate)
SQL agent jobs run hourly and daily to sync specific objects to cached database
Monitor bulk API jobs in Salesforce: Setup → Bulk Data Load Jobs
Check API usage at Setup → Company Information (259K requests/24hrs rolling limit in production)
Set up API usage notifications: Setup → API Usage Notifications (set to 85% threshold)
Create the database first manually; DBAmp creates tables within it automatically
Monitor API usage daily for first 2 weeks, then 2-3 times weekly to establish baseline
Pull only necessary objects - avoid syncing all Salesforce objects to cache database
Use linked server (SF Stage) to query Salesforce data via SQL Server
Large batch imports auto-split into 10,000 record batches by DBAmp

2:37 "some things you should consider, you know, day-to-day,"
7:52 "important to us for all of these usage patterns."
15:58 "When you're looking at this, you should be worrying about production,"
16:52 "because it's not going to be 5 million, it's going to be 200,000."
18:21 "So note that we are in staging and you go to set up and you can look at company"
22:22 "That would be really important to understand and in weeks 3 to 8, you know,"
23:26 "We purchase additional API calls because we need it. Whatever it has to do,"
25:49 "It wouldn't know what to do because the the the field that did not match exactly"

Item	Value/Setting	Timestamp	Notes
Review video	Add settings	Add timestamp	Add notes