<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Rudi Bruchez</title><link>https://www.pachadata.com/en/tags/architecture/</link><description>Recent content in Architecture on Rudi Bruchez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 28 Aug 2026 16:40:55 +0200</lastBuildDate><atom:link href="https://www.pachadata.com/en/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Why you should NOT multiply SQL Server instances</title><link>https://www.pachadata.com/en/docs/howtos/administration/instances/</link><pubDate>Tue, 27 Jan 2026 00:00:00 +0000</pubDate><guid>https://www.pachadata.com/en/docs/howtos/administration/instances/</guid><description>&lt;div class="alert alert-success" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;TL;DR&lt;/div&gt;&#10;&lt;p&gt;Installing several instances on the same production server is almost never necessary. Consolidate all your databases onto one instance.&lt;/p&gt;&#10;&lt;p&gt;A single instance gives you better performance, better visibility and simpler operations.&lt;/p&gt;&#10;&lt;p&gt;Having to support different SQL Server versions per database is not an argument for several instances. The database compatibility level handles that.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="why-do-people-install-several-instances-on-one-server"&gt;Why do people install several instances on one server?&lt;/h2&gt;&#10;&lt;p&gt;In a world of virtualisation and containers, a system administrator&amp;rsquo;s natural reflex is to isolate: one application, one service, one instance.&lt;/p&gt;</description></item></channel></rss>