<story><title>LLM as Database Administrator (2023)</title><url>https://arxiv.org/abs/2312.01454</url></story><parent_chain></parent_chain><comment><author>Simon_ORourke</author><text>Any LLM would outperform the DBA we had in our first start-up. This guy was a buddy of the co-founder and was parachuted into the top paying IC role out of about 25 developers.&lt;p&gt;His &amp;quot;achievements&amp;quot; included dropping the production database by messing with the backup processes, insisting on very wide tables rather than smaller tables with joins since &amp;quot;they&amp;#x27;re easier to maintain&amp;quot;, and giving out full admin rights to junior devs who subsequently went on to develop their own &amp;quot;black data mart&amp;quot; which was way way better than the production version.&lt;p&gt;Sigh, and to make things worse, this DBA guy managed to leverage his &amp;quot;experience&amp;quot; into a Principal Data Architect role at a major consulting company after the start-up predictably imploded.</text></comment>
<story><title>LLM as Database Administrator (2023)</title><url>https://arxiv.org/abs/2312.01454</url></story><parent_chain></parent_chain><comment><author>tarsinge</author><text>This is not the original title, which is &amp;quot;Database Diagnosis System using Large Language Models&amp;quot;. LLM as a diagnosis tool seems indeed like a really good use case as the paper show, but the changed title imply the point is replacing the whole role.</text></comment>