<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Database on Stefan Maron | Business Central &amp; AL Development</title><link>https://stefanmaron.com/tags/database/</link><description>Recent content in Database on Stefan Maron | Business Central &amp; AL Development</description><generator>Hugo -- gohugo.io</generator><language/><lastBuildDate>Thu, 10 Sep 2026 07:33:46 +0200</lastBuildDate><atom:link href="https://stefanmaron.com/tags/database/index.xml" rel="self" type="application/rss+xml"/><item><title>bcdb restore: Write a Cloud Export Into a Container</title><link>https://stefanmaron.com/posts/bcdb-restore-write-a-cloud-export-into-a-container/</link><pubDate>Thu, 10 Sep 2026 07:33:46 +0200</pubDate><guid>https://stefanmaron.com/posts/bcdb-restore-write-a-cloud-export-into-a-container/</guid><description>bcdb could already open a .bak or a .bacpac and read anything in it, no SQL Server involved. That was genuinely useful for AL Runner , which is why I built it in the first place, but it didn&amp;rsquo;t do much for a developer&amp;rsquo;s normal day. For that, you want the data sitting in a database you can query, click through, and run BC against.
Since v0.2.0, bcdb restore is what changes that: it writes a source&amp;rsquo;s rows straight into a container that&amp;rsquo;s already running, and it doesn&amp;rsquo;t ask the container&amp;rsquo;s schema to match the source first.</description></item><item><title>Introducing bcdb: Read a Business Central Backup Without SQL Server</title><link>https://stefanmaron.com/posts/bcdb-read-business-central-backups-without-sql-server/</link><pubDate>Tue, 01 Sep 2026 09:40:40 +0200</pubDate><guid>https://stefanmaron.com/posts/bcdb-read-business-central-backups-without-sql-server/</guid><description>Say someone hands you a customer&amp;rsquo;s BC backup and you need to check one field on one table. The normal path is: find or spin up a SQL Server, restore the file, wait for however long that takes on however large the database is, connect, query, and then decide whether to keep that SQL Server around or tear it down. All of that just to read a handful of values.</description></item><item><title>How Do Database Transactions Actually Work in Business Central?</title><link>https://stefanmaron.com/posts/bc-database-transactions-deep-dive/</link><pubDate>Sun, 15 Sep 2024 09:00:00 +0100</pubDate><guid>https://stefanmaron.com/posts/bc-database-transactions-deep-dive/</guid><description>I thought I knew how transactions worked in Business Central. Then I started actually testing them, and I was genuinely shocked by a few things. This stream is me working through it live, building a small test extension and watching what commits and errors actually do to the database.
The full stream is on YouTube — this post covers the key findings. All the code from the stream ended up at github.</description></item><item><title>Table Keys and SQL Indexes in Business Central</title><link>https://stefanmaron.com/posts/table-keys-and-sql-indexes-in-business-central/</link><pubDate>Sat, 20 Jul 2024 09:00:00 +0100</pubDate><guid>https://stefanmaron.com/posts/table-keys-and-sql-indexes-in-business-central/</guid><description>I&amp;rsquo;ve wanted to dig into this topic properly for a long time. How do AL table keys actually translate to SQL Server indexes? What SQL does Business Central generate from your AL queries? And does adding a key actually help — or can it hurt? This stream was my attempt to answer all of that with real numbers.
The full stream is on YouTube: Table keys and SQL Indexes – The BC Coding Stream The test setup I used waldo&amp;rsquo;s BCPerfTool as the harness.</description></item><item><title>Automated export objects from C/AL</title><link>https://stefanmaron.com/posts/automated-export-objects-from-c-al/</link><pubDate>Mon, 07 Sep 2020 05:44:17 +0000</pubDate><guid>https://stefanmaron.com/posts/automated-export-objects-from-c-al/</guid><description>This time I have some tips on how to use GIT integration when developing in C/AL with docker. When used to AL development one of the first things to notice when going back to C/AL is, that you do not have any version control.
To solve this problem, I added a little bit of SQL code to the [Object] table as SQL Trigger. This trigger exports each edited object as TXT file to specified folder.</description></item><item><title>Coding4Performance 5: FindSet vs FindFirst</title><link>https://stefanmaron.com/posts/coding4performance-5-findset-vs-findfirst/</link><pubDate>Thu, 23 Jul 2020 06:26:19 +0000</pubDate><guid>https://stefanmaron.com/posts/coding4performance-5-findset-vs-findfirst/</guid><description>Today in coding for performance, we talk a bit about FindSet and FindFirst. I actually had plans to make this one the first post in this series. But it turned out that the differences between this two commands are not as obvious as I first thought.
Let me first place a huge disclaimer here: Everything I test and explain here is done with Business Central version 16. It might be that earlier versions of BC and NAV behaved differently.</description></item></channel></rss>