# Implementing Data Synchronization from Raspberry Pi to Central SQL Server

**URL:** https://discourse.nodered.org/t/implementing-data-synchronization-from-raspberry-pi-to-central-sql-server/87483
**Category:** Industrial
**Tags:** database
**Created:** [25 April 2024 10:12 UTC](https://discourse.nodered.org/t/implementing-data-synchronization-from-raspberry-pi-to-central-sql-server/87483 "2024-04-25T10:12:26Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [25 April 2024 10:35 UTC](https://discourse.nodered.org/t/implementing-data-synchronization-from-raspberry-pi-to-central-sql-server/87483/2 "2024-04-25T10:35:39Z")

</div>

> [@thahamp](#):
>
> ensuring that only new data is copied to the SQL server. How can I achieve this

No doubt you can craft your SQL or the database schema so that no duplicates get into MSSQL.

I'd probably use MQTT to pass the SQL statement from the Pi to the server. It's not trivial to guarantee delivery over an unreliable network but there are [posts here describing an approach](https://discourse.nodered.org/t/announce-improved-guaranteed-delivery-flow/39877).

Use the same mechanism to pass back a list of inserted records and set a "transferred" flag in SQLite for reference in 5 minutes time.

---

_[View the full topic](https://discourse.nodered.org/t/implementing-data-synchronization-from-raspberry-pi-to-central-sql-server/87483)._