<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Internals on Andy M Mallon - AM²</title><link>https://am2.co/tag/internals/</link><description>Recent content in Internals on Andy M Mallon - AM²</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 18 Oct 2021 09:00:15 -0400</lastBuildDate><atom:link href="https://am2.co/tag/internals/index.xml" rel="self" type="application/rss+xml"/><item><title>What the heck is the SSISDB? Where does it come from?</title><link>https://am2.co/2021/10/18/what-the-heck-is-the-ssisdb-where-does-it-come-from/</link><pubDate>Mon, 18 Oct 2021 09:00:15 -0400</pubDate><guid>https://am2.co/2021/10/18/what-the-heck-is-the-ssisdb-where-does-it-come-from/</guid><description>&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=r3AP26ywQsQ" rel="noopener" target="_blank"&gt;&lt;img src="https://am2.co/wp-content/uploads/photo-1619793644997-6f55d1c3cb5c-1024x683.jpg" alt="Two ducks ducking" width="400" height="267" class="alignright size-large wp-image-9636" /&gt;&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;Back in my day, we stored SQL Server Integration Services (SSIS) packages in msdb, or the file system. Well, I&amp;rsquo;m neither dead nor retired, so that&amp;rsquo;s not an accurate statement&amp;ndash;today is still &amp;ldquo;my time.&amp;rdquo; But when I was learning about SQL Server, those were the only two options. If you or your environment predate SQL Server 2012, then you might only be familiar with those two options.&lt;/p&gt;</description></item><item><title>Transaction log growth during BACKUP</title><link>https://am2.co/2017/04/10/transaction-log-growth-backup/</link><pubDate>Mon, 10 Apr 2017 08:06:37 -0400</pubDate><guid>https://am2.co/2017/04/10/transaction-log-growth-backup/</guid><description>&lt;p&gt;Over on Stack Exchange, &lt;a href="http://dba.stackexchange.com/questions/169174/sql-server-2014-transaction-log-is-growing-very-fast" target="_blank"&gt;someone asked&lt;/a&gt; why their transaction log was growing very fast during a full backup. An interesting tidbit to this question is that the database is in &lt;code&gt;SIMPLE&lt;/code&gt; recovery &amp;ndash; so the log should stay tiny, right?&lt;/p&gt;&#10;&lt;p&gt;Wrong. While taking a full backup of the database, SQL Server is unable to reuse the transaction log for the duration of the backup, &lt;em&gt;even if the database is in &lt;code&gt;SIMPLE&lt;/code&gt; recovery&lt;/em&gt;. If your database is very busy, or backups take a long period of time, this can require a large transaction log, &lt;em&gt;even if the database is in &lt;code&gt;SIMPLE&lt;/code&gt; recovery&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Nonclustered index storage on clustered columnstore</title><link>https://am2.co/2017/01/06/nonclustered-index-storage-on-clustered-columnstore/</link><pubDate>Fri, 06 Jan 2017 11:47:02 -0500</pubDate><guid>https://am2.co/2017/01/06/nonclustered-index-storage-on-clustered-columnstore/</guid><description>&lt;p&gt;&lt;a href="https://dba.stackexchange.com/q/160158/52344"&gt;&lt;img src="https://am2.co/images/stack-exchange-question-mark.svg" alt="Question on Stack Exchange" width="96" height="96" class="stack-exchange-question-icon" /&gt;&lt;/a&gt;&lt;/p&gt;&#10;&lt;h2 id="question"&gt;Question&lt;/h2&gt;&#10;&lt;p&gt;In SQL Server, a non-unique nonclustered index on a rowstore table incorporates the base object&amp;rsquo;s &lt;em&gt;bookmark&lt;/em&gt; (RID or clustering key) at all levels of the nonclustered index structure. The bookmark is stored as part of the nonclustered index &lt;em&gt;key&lt;/em&gt; at all index levels.&lt;/p&gt;</description></item></channel></rss>