<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fabric on Jan-V.nl</title><link>https://jan-v.nl/tags/fabric/</link><description>Recent content in Fabric on Jan-V.nl</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2006-2026 Jan-V.nl All Rights Reserved.</copyright><lastBuildDate>Wed, 03 Jun 2026 09:45:17 +0200</lastBuildDate><atom:link href="https://jan-v.nl/tags/fabric/index.xml" rel="self" type="application/rss+xml"/><item><title>Build your own Fabric Capacity usage functionality</title><link>https://jan-v.nl/post/2026/build-your-own-fabric-capacity-usage-functionality/</link><pubDate>Wed, 03 Jun 2026 09:45:17 +0200</pubDate><guid>https://jan-v.nl/post/2026/build-your-own-fabric-capacity-usage-functionality/</guid><description>I use Microsoft Fabric on a project to store all customer data. Each customer gets their own workspace, so data is isolated. While Microsoft Fabric has its challenges and comes with a hefty price, it does bring quite a lot of useful data solutions under one umbrella. If you only need to store data in a (simple) database there are many more solutions that will fit your use case better. For my project we need to do ingestion, transformation, cleansing, store structured data, store unstructured data, etc.</description></item></channel></rss>