Skip to content
CRM ⇄ Database

Dun And Bradstreet to SQL Server integration — real-time data sync

Keep Dun And Bradstreet and SQL Server in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Dun And Bradstreet and SQL Server

Treat Dun And Bradstreet like part of your database: its records live in SQL Server as real tables, and writes in either place sync to the other in seconds.

Dun And Bradstreet is a read-only source: Stacksync reads its data in real time and delivers it into SQL Server, so SQL Server always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.

Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in SQL Server, where it can be queried and joined like everything else.

Common use cases

  • 01 Sync the D&B corporate family tree (parent and subsidiary DUNS) into the CRM so ABM and territory owners see full account hierarchies and roll pipeline up to the global ultimate.
  • 02 Build target-account lists with Criteria Search and land the resulting DUNS plus firmographics in a database for outbound and TAM analysis.
  • 03 Expose SaaS records as SQL Server tables that existing SSRS reports and internal apps can query
  • 04 Mirror on-premises ERP data held in SQL Server into cloud CRM and support systems

Common sync patterns

Query the CRM like a database

Accounts, contacts, and custom objects from Dun And Bradstreet become tables in SQL Server you can join with application data directly.

Product events onto CRM records

Signup, usage, or lifecycle changes written to SQL Server sync onto the matching records in Dun And Bradstreet, giving go-to-market teams live product context.

Internal tools without API code

Back-office apps read and write the synced tables; Stacksync handles the Dun And Bradstreet API, limits, and retries.

What you can sync between Dun And Bradstreet and SQL Server

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Dun And Bradstreet objects SQL Server objects How this pairing syncs
Criteria Search Query companies by firmographic criteria (industry, geography, size) and get back a list of D-U-N-S Numbers to enrich; read-only list building. Columns Field-level mapping targets with T-SQL types. Criteria Search is specific to Dun And Bradstreet and Columns to SQL Server — each maps to any object or custom field on the other side.
Monitoring Notifications Change notices for a registered portfolio of DUNS; read-only feed pulled from the notifications endpoint (retained ~60 days) or delivered as bundled push. Primary and Unique Keys Match keys for idempotent upserts and conflict handling. Monitoring Notifications is specific to Dun And Bradstreet and Primary and Unique Keys to SQL Server — each maps to any object or custom field on the other side.
Company Information (Data Block) Core firmographics for a D-U-N-S Number - legal name, addresses, industry codes, employees, sales, status. Retrieved read-only via the Enrich endpoint; blocks come in levels L1-L4. CDC Change Tables System-populated tables holding captured inserts, updates, and deletes for consumers. Company Information (Data Block) is specific to Dun And Bradstreet and CDC Change Tables to SQL Server — each maps to any object or custom field on the other side.
Principals & Contacts (Data Block) Company officers, executives, and contacts tied to a D-U-N-S Number; read-only enrichment used to populate CRM contact and account-owner fields. Stored Procedures T-SQL logic that can validate or post-process synced rows. Principals & Contacts (Data Block) is specific to Dun And Bradstreet and Stored Procedures to SQL Server — each maps to any object or custom field on the other side.
Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. Databases Instance-level databases that scope a sync's reads and writes. Company Hierarchy & Connections (Family Tree) is specific to Dun And Bradstreet and Databases to SQL Server — each maps to any object or custom field on the other side.
Financial Strength & Risk Insight (Data Block) D&B risk and credit signals - D&B Rating, PAYDEX, Failure Score, Delinquency Score, Viability - keyed by D-U-N-S Number; read-only. Schemas Namespaces (dbo and custom) used to organize synced tables. Financial Strength & Risk Insight (Data Block) is specific to Dun And Bradstreet and Schemas to SQL Server — each maps to any object or custom field on the other side.

How changes propagate between Dun And Bradstreet and SQL Server

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Dun And Bradstreet SQL Server Interval-based propagation

DetectionStacksync polls Dun And Bradstreet for changes on an incremental schedule, reading only records changed since the previous pass. Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days).

DeliveryEach detected change is applied to SQL Server as a row-level write, with types converted between the two schemas.

SQL Server Dun And Bradstreet Sub-second propagation

DetectionChanges in SQL Server are captured at the source via change data capture — no polling loop against its API. SQL Server Native Change Data Capture (CDC).

DeliveryDun And Bradstreet does not accept inbound record writes, so this direction carries requests rather than records: Dun And Bradstreet's output flows back as field updates on the originating SQL Server records.

Rate-limit considerations

  • Dun And Bradstreet: Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
  • SQL Server: No API rate limits; throughput depends on instance resources, licensing tier, and connection limits.
What ships with Dun And Bradstreet ⇄ SQL Server

Connect Dun And Bradstreet and SQL Server for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dun And Bradstreet–SQL Server connection.

Real-time

Real-time sync

Changes in Dun And Bradstreet or SQL Server instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dun And Bradstreet or SQL Server data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Dun And Bradstreet or SQL Server record.

Observability

Monitoring

Track your Dun And Bradstreet ⇄ SQL Server sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dun And Bradstreet and SQL Server.

How the Dun And Bradstreet and SQL Server connectors work

Dun And Bradstreet

Integration surface
D&B Direct+ REST API (plus.dnb.com) - capability groups for Identity Resolution (Match), Search, Enrich (Data Blocks by D-U-N-S Number), Multi-Process, Data File/Batch, and Monitoring
Authentication
OAuth 2.0 client-credentials: Base-auth a consumer key/secret to POST /v3/token for a bearer token; access tokens expire after 24 hours.
Change detection
Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days). Bundled push delivery is configured with your D&B rep; there is no standard HTTP webhook and no log-based CDC.
Capabilities
read
Rate limits
Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.

SQL Server

Integration surface
SQL over the TDS wire protocol (Tabular Data Stream), via ODBC/JDBC/ADO.NET drivers
Authentication
Database credentials entered as a connection string or as parameters (host/user/password) in the Create New Sync page
Change detection
SQL Server Native Change Data Capture (CDC); a DBA runs a one-time setup script with sysadmin privileges to enable CDC and create Stacksync wrapper procedures
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput depends on instance resources, licensing tier, and connection limits
SQL Server setup guide
How it works

How to connect Dun And Bradstreet to SQL Server — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Dun And Bradstreet and SQL Server with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Dun And Bradstreet connected
    SQL Server connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dun And Bradstreet and SQL Server objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Dun And Bradstreet ⇄ SQL Server
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Dun And Bradstreet SQL Server
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Dun And Bradstreet and SQL Server integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 516 integrations available for Dun And Bradstreet and SQL Server.

Popular · 7 of 516
All Dun And Bradstreet integrations All SQL Server integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own