Skip to content
Storage ⇄ Database

Box to SQL Server integration — real-time, two-way sync

Keep Box 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 Box and SQL Server

Keep SQL Server and Box in step: a row in SQL Server for every file in Box, with names, paths, metadata, and status staying consistent in real time, in both directions.

A database holds structured records; a storage system holds the files those records depend on, such as contracts, images, exports, uploads, and documents. The two describe the same things from opposite sides: a row in SQL Server says a file exists and carries its name, location, and status, while Box holds the bytes. Linked only by a hand-kept path or a one-off script, the two drift the moment a file is renamed, moved, or deleted and the record still points at where it used to be.

Stacksync syncs Stored Procedures, Databases, Schemas, Tables in SQL Server with Groups, Tasks, Events, Files in Box bi-directionally and in real time. File attributes, including name, path or object key, size, type, modified time, owner, and tags or custom properties, map field by field to columns on the matching row, and a change on either side shows up on the other within seconds. New files appear as rows, metadata edits travel in the direction you choose, and deletes stay consistent, with conflict rules you set in place of nightly reconciliation scripts.

Common use cases

  • 01 Mirror on-premises ERP data held in SQL Server into cloud CRM and support systems
  • 02 Feed a cloud warehouse from SQL Server continuously using native CDC instead of SSIS batch jobs
  • 03 Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.
  • 04 Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.

Common sync patterns

A queryable index of the file store

Every file or object in Box shows up as a row in SQL Server, with its name, folder or key, size, type, and modified date as columns, so the contents of the store can be listed, filtered, and joined like any other table.

File metadata kept in step

Tags, custom properties, owner, or status columns edited on a row in SQL Server write back to the matching file's metadata in Box, and metadata changed in Box updates the row, so the two never disagree about a file.

Records that point at documents

Where a record in SQL Server references a file in Box, such as a contract, an image, an export, or an upload, the reference, path, and status stay consistent as files are renamed, moved, or replaced, so stored links keep resolving.

What you can sync between Box 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.

Box objects SQL Server objects How this pairing syncs
Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. Primary and Unique Keys Match keys for idempotent upserts and conflict handling. Collaborations is specific to Box and Primary and Unique Keys to SQL Server — each maps to any object or custom field on the other side.
Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. CDC Change Tables System-populated tables holding captured inserts, updates, and deletes for consumers. Users is specific to Box and CDC Change Tables to SQL Server — each maps to any object or custom field on the other side.
Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. Stored Procedures T-SQL logic that can validate or post-process synced rows. Groups is specific to Box and Stored Procedures to SQL Server — each maps to any object or custom field on the other side.
Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. Databases Instance-level databases that scope a sync's reads and writes. Tasks is specific to Box and Databases to SQL Server — each maps to any object or custom field on the other side.
Events Enterprise admin event stream, an audit log of uploads, deletes, logins, and shares across the account; read-only, consumed for reporting or change feeds. Schemas Namespaces (dbo and custom) used to organize synced tables. Events is specific to Box and Schemas to SQL Server — each maps to any object or custom field on the other side.
Files Core content object with versions, name, size, and metadata; synced two-way so files and their attributes move between Box and a database or another store. Tables The primary sync target; rows map to records in connected systems. Files is specific to Box and Tables to SQL Server — each maps to any object or custom field on the other side.

How changes propagate between Box 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.

Box SQL Server Sub-second propagation

DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.

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

SQL Server Box 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).

DeliveryEach detected change is written to Box through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
  • SQL Server: No API rate limits; throughput depends on instance resources, licensing tier, and connection limits.
What ships with Box ⇄ SQL Server

Connect Box and SQL Server for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Box 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 Box or SQL Server record.

Observability

Monitoring

Track your Box ⇄ 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 Box and SQL Server.

How the Box and SQL Server connectors work

Box

Integration surface
REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
Authentication
OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
Change detection
V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
Capabilities
read · write · webhooks
Rate limits
Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.

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 Box 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 Box 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
    Box connected
    SQL Server connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Box 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 · Box ⇄ 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
    Box SQL Server
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Box 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
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 530 integrations available for Box and SQL Server.

Popular · 7 of 530
All Box 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