<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Dotnet on Pavel Gelver</title>
    <link>https://pavelgelver.com/tags/dotnet/</link>
    <description>Recent content in Dotnet on Pavel Gelver</description>
    <generator>Hugo -- 0.150.0</generator>
    <language>en</language>
    <lastBuildDate>Mon, 08 Sep 2025 21:00:00 +0200</lastBuildDate>
    <atom:link href="https://pavelgelver.com/tags/dotnet/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Sp or Not Sp pt.2</title>
      <link>https://pavelgelver.com/posts/sp-or-not-sp-pt2/</link>
      <pubDate>Mon, 08 Sep 2025 21:00:00 +0200</pubDate>
      <guid>https://pavelgelver.com/posts/sp-or-not-sp-pt2/</guid>
      <description>&lt;p&gt;In the first article in this two-part series, we analyzed the difference between copying using EF and copying using a stored procedure. Now, let&amp;rsquo;s see &lt;strong&gt;how much&lt;/strong&gt; faster the stored procedure is and compare the performance of both approaches: ORM vs SP.&lt;/p&gt;
&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;
&lt;p&gt;If you haven&amp;rsquo;t read the first part of the article yet, I strongly recommend reading it here: &lt;a href=&#34;https://pavelgelver.com/posts/sp-or-not-sp&#34;&gt;Sp or Not Sp&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;You can find all the code from this article in the GitHub repository here: &lt;a href=&#34;https://github.com/gelverpl/pavelgelver.com-articles/tree/master/sp-or-not-sp-pt2&#34; rel=&#34;external&#34; target=&#34;_blank&#34;&gt;pavelgelver.com-articles/sp-or-not-sp-pt2&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sp or Not Sp</title>
      <link>https://pavelgelver.com/posts/sp-or-not-sp/</link>
      <pubDate>Wed, 13 Aug 2025 21:00:13 +0200</pubDate>
      <guid>https://pavelgelver.com/posts/sp-or-not-sp/</guid>
      <description>Harmless-looking EF Core code can bottleneck performance. Let’s unpack why stored procedures might be better and how team habits play a role.</description>
    </item>
  </channel>
</rss>
