---
title: "Set up the SQL Writer endpoint"
slug: "bc-set-up-the-sql-writer-endpoint"
description: "Learn to use the SQL Writer endpoint to write XML data from Dynamics 365 Business Central to SQL Server effortlessly, with no extra programming needed."
tags: ["BC", "BIS", "Business Central", "Business Integration Solutions", "Task"]
updated: 2026-06-25T09:59:05Z
published: 2026-06-25T09:59:05Z
canonical: "docs.staedean.com/bc-set-up-the-sql-writer-endpoint"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up the SQL Writer endpoint

Use the **SQL Writer** endpoint to write XML data generated by Microsoft Dynamics 365 Business Central to SQL Server and process the data into the SQL tables.

The **SQL Writer** endpoint expects data to write to a SQL Server database connected using the specified connection string. This variant of the writer uses automatic mode, so no further programming is required in SQL Server. The connection string must be in the appropriate format and must at minimum contain the server name, database name, and authentication information.

## Prerequisites

- Access to a SQL Server database.
- A connection string to the SQL Server database that allows the Microsoft Dynamics 365 Business Central service tier user to connect and write data. This is required when the user running the Microsoft Dynamics 365 Business Central service tier does not have access to that environment.

## Steps

1. Define an external document definition for the SQL Server tables and fields to write. Before designing the document, set the subtype of the document to **SQL** and fill in the connection details. This lets you create a document structure similar to internal documents.
2. Include the **SQL Writer** endpoint in the pipeline.
3. Set the SQL document as **Document No.** in the **SQL Writer** endpoint.
4. Select **Check Configuration** to validate the external document definition and test the SQL connection.
5. Optionally, enable **Omit Output**. This lets write transactions proceed on tables that have triggers set. Note that when enabled and a query executes but rows modified is 0, no error is reported. If unsure, leave **Omit Output** at its default value (false).

![SQL Writer](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/BIS_SQLWriter.png)

## Related

- [SQLWRITER endpoint](/bc-sqlwriter-endpoint.md)