<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results matching tags 'DBA', 'Agile', and 'What a DBA Does'</title><link>http://sqlblog.com/search/SearchResults.aspx?o=DateDescending&amp;tag=DBA,Agile,What+a+DBA+Does&amp;orTags=0</link><description>Search results matching tags 'DBA', 'Agile', and 'What a DBA Does'</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>It's all about the data...</title><link>http://sqlblog.com/blogs/james_luetkehoelter/archive/2008/06/16/it-s-all-about-the-data.aspx</link><pubDate>Mon, 16 Jun 2008 15:33:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:7319</guid><dc:creator>James Luetkehoelter</dc:creator><description>&lt;P&gt;I read a very interesting post on &lt;A class="" href="http://www.sqlskills.com/blogs/kimberly/2008/06/08/IndexesInSQLServer20052008Part2Internals.aspx"&gt;Kimberly Tripp's blog&lt;/A&gt; which was about indexing, but she had a very interesting set of requirements for good indexing that I think apply to everything when designing, tuning, backing up, etc., any database.&amp;nbsp;What strikes me the most are 1) and 2) - how can you tune any sort of system if you don't really know what the data *is* and how it is used? As Kim says: &lt;/P&gt;
&lt;P&gt;&lt;FONT face=Calibri color=#000000 size=3&gt;"So, what is â€œfinding the right balanceâ€ in indexing? In my opinion, there are three requirements/pre-requisites: &lt;/FONT&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;DIV class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT face=Calibri color=#000000 size=3&gt;knowing the data&lt;/FONT&gt;&lt;/DIV&gt;
&lt;LI&gt;
&lt;DIV class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT face=Calibri color=#000000 size=3&gt;knowing how the users use the data &lt;/FONT&gt;&lt;/DIV&gt;
&lt;LI&gt;
&lt;DIV class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT face=Calibri color=#000000 size=3&gt;knowing how the underlying structures and database stores/manipulates and uses indexes"&lt;/FONT&gt;&lt;/DIV&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;P class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;I can't count how many times I've run into clients where I'm asked to tune or create a disaster recovery plan or secure&amp;nbsp;for a database where no one is really sure what things mean and how it is used. Everyone should start here, and I'd take it to the step of actually know not just the data, but the &lt;EM&gt;information&lt;/EM&gt;; that is, what is the business meaning behind the data. It's a mantra to adopt - "Know thy data".&lt;/P&gt;</description></item></channel></rss>