<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DBA on AdaTheDev Blog</title><link>https://www.adathedev.co.uk/tags/dba/</link><description>Recent content in DBA on AdaTheDev Blog</description><generator>Hugo -- gohugo.io</generator><managingEditor>adathedev@gmail.com (Adrian Hills)</managingEditor><webMaster>adathedev@gmail.com (Adrian Hills)</webMaster><lastBuildDate>Thu, 04 Mar 2010 21:30:00 +0000</lastBuildDate><atom:link href="https://www.adathedev.co.uk/tags/dba/index.xml" rel="self" type="application/rss+xml"/><item><title>Rise of the SQL Server DevBA</title><link>https://www.adathedev.co.uk/2010/03/rise-of-sql-server-devba.html</link><pubDate>Thu, 04 Mar 2010 21:30:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2010/03/rise-of-sql-server-devba.html</guid><description>Something that has got me thinking recently is the distinction between an SQL Server Developer and a DBA. I imagine that most people would describe themselves as one or the other exclusively. My CV for example says I&amp;rsquo;m a developer - that is what I am. I would never market myself as a DBA; aside from the fact I just don&amp;rsquo;t have the full skillset of a DBA, it would just be an insult to the real DBAs out there whose knowledge and experience in that arena far outweighs mine.</description></item></channel></rss>