<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Database Optimization on DataFrame</title>
    <link>https://dataframe.hr/tags/database-optimization/</link>
    <description>Recent content in Database Optimization on DataFrame</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 10 Jun 2023 00:00:00 +0200</lastBuildDate>
    <atom:link href="https://dataframe.hr/tags/database-optimization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Index maintenance in Azure SQL Database</title>
      <link>https://dataframe.hr/azure-synapse/index-maintenance-in-azure-sql-database/</link>
      <pubDate>Sat, 10 Jun 2023 00:00:00 +0200</pubDate>
      <guid>https://dataframe.hr/azure-synapse/index-maintenance-in-azure-sql-database/</guid>
      <description>One task that is often overlooked by DBAs is automated index maintenance in Azure SQL Database. On-premises administrators may be used to the simplicity of maintenance plans, but these are not available for Azure SQL DB (for now).&#xA;Luckily, Ola Hallengren has provided SQL Server Maintenance Solution under an MIT license which includes many valuable scripts related to database administration.&#xA;Required objects We only need a couple of objects for index maintenance so instead of downloading the whole solution, you can focus on the following:</description>
    </item>
    <item>
      <title>Slow queries in the application</title>
      <link>https://dataframe.hr/sql-server/slow-queries-in-the-application/</link>
      <pubDate>Thu, 22 Dec 2022 00:00:00 +0200</pubDate>
      <guid>https://dataframe.hr/sql-server/slow-queries-in-the-application/</guid>
      <description>Ever wondered why you encounter slow queries in the application, but they work fine from SSMS?&#xA;I’m sure everyone encounters this issue sooner or later and it has many variations, so I’ll focus on the one I encounter most often.&#xA;Common scenario You produce a great stored procedure, test it meticulously, it passes QA, ends up on production, and everyone is happy. Then couple of months later the client reports a timeout.</description>
    </item>
  </channel>
</rss>
