<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: SQL Server groups - ITPro or Dev?</title>
	<atom:link href="http://msdev.thepodcastnetwork.com/2006/09/20/sql-server-groups-itpro-or-dev/feed/" rel="self" type="application/rss+xml" />
	<link>http://msdev.thepodcastnetwork.com/2006/09/20/sql-server-groups-itpro-or-dev/</link>
	<description>Your Passion...Your Potential</description>
	<pubDate>Fri,  5 Dec 2008 09:42:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Brian H. Madsen</title>
		<link>http://msdev.thepodcastnetwork.com/2006/09/20/sql-server-groups-itpro-or-dev/#comment-1611</link>
		<dc:creator>Brian H. Madsen</dc:creator>
		<pubDate>Wed, 20 Sep 2006 07:40:13 +0000</pubDate>
		<guid isPermaLink="false">http://msdev.thepodcastnetwork.com/2006/09/20/sql-server-groups-itpro-or-dev/#comment-1611</guid>
		<description>Nick, it's actually been discussed often - especially between the UGs..

one aspect i think is sad is that the seems to be nearly a 100% agreement that a DBA isn't needed because the developer does the magic on the DB..

it's one item which is neglected in a LOT of corporations today and generally isn't something that's attended to until you start having issues with your database.

In terms of the roles on the database...Developer vs. Database Administrator...then i have to say that sadly (very sadly) you don't see that many developers with enough skills to implement a database properly - especially around performance issues..i don't know how many times i've seen a half-arsed database schema been presented, then in the next step get a bad excuse about not being a DBA.

So - after having had these discussions in the past i see one problem here...it's a self-styled conclusion that some may, or may not, agree with. Firstly, a DBA is NOT meant to design databases, set up indexes etc...a DBD (Database Designer) is meant to do that..it's one role which is constantly overlooked..So to compare roles is fairly impossible since we're neglecting to include that one vital role.

Also,with a proper scoped project, you would know what type of data you're looking for - otherwise how can you design the database? - and this means that the DBD can design the database, write the queries that is needed..setup the triggers, stored procedures etc..

Now, back to where do we fit in, as a UG in the industry, i'd say in the IT Pro group..unless you want to fight semantics and argue that SQL Server now as CLR integration, so therefore it must be a Dev grouping..fundamentally i'd say IT Pro.

Anyways, my $2.75 worth of bandwidth is spent :)</description>
		<content:encoded><![CDATA[<p>Nick, it&#8217;s actually been discussed often - especially between the UGs..</p>
<p>one aspect i think is sad is that the seems to be nearly a 100% agreement that a DBA isn&#8217;t needed because the developer does the magic on the DB..</p>
<p>it&#8217;s one item which is neglected in a LOT of corporations today and generally isn&#8217;t something that&#8217;s attended to until you start having issues with your database.</p>
<p>In terms of the roles on the database&#8230;Developer vs. Database Administrator&#8230;then i have to say that sadly (very sadly) you don&#8217;t see that many developers with enough skills to implement a database properly - especially around performance issues..i don&#8217;t know how many times i&#8217;ve seen a half-arsed database schema been presented, then in the next step get a bad excuse about not being a DBA.</p>
<p>So - after having had these discussions in the past i see one problem here&#8230;it&#8217;s a self-styled conclusion that some may, or may not, agree with. Firstly, a DBA is NOT meant to design databases, set up indexes etc&#8230;a DBD (Database Designer) is meant to do that..it&#8217;s one role which is constantly overlooked..So to compare roles is fairly impossible since we&#8217;re neglecting to include that one vital role.</p>
<p>Also,with a proper scoped project, you would know what type of data you&#8217;re looking for - otherwise how can you design the database? - and this means that the DBD can design the database, write the queries that is needed..setup the triggers, stored procedures etc..</p>
<p>Now, back to where do we fit in, as a UG in the industry, i&#8217;d say in the IT Pro group..unless you want to fight semantics and argue that SQL Server now as CLR integration, so therefore it must be a Dev grouping..fundamentally i&#8217;d say IT Pro.</p>
<p>Anyways, my $2.75 worth of bandwidth is spent :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phillip Molly Malone</title>
		<link>http://msdev.thepodcastnetwork.com/2006/09/20/sql-server-groups-itpro-or-dev/#comment-1603</link>
		<dc:creator>Phillip Molly Malone</dc:creator>
		<pubDate>Wed, 20 Sep 2006 01:01:50 +0000</pubDate>
		<guid isPermaLink="false">http://msdev.thepodcastnetwork.com/2006/09/20/sql-server-groups-itpro-or-dev/#comment-1603</guid>
		<description>Interesting point. I know with Progress installs its normally the developers that decide all that stuff as there isn't the high need for a DBA that there is in other DBs like MS SQL and Oracle. I think developers really do need to understand the issues of indexing and the likes but having said that, DBA's will still be able to do things to improve performance.

Plus there is more and more 3rd party products quering our databases that the orginial developer doesn't necessarily have any control over. Things like Crystal, Data ware houses and other BI solutions like &lt;a href="www.easyask.com" rel="nofollow"&gt;EasyAsk&lt;/a&gt; (a natural language search BI tool for Progress (NB: I work for PRGS)).

Molly</description>
		<content:encoded><![CDATA[<p>Interesting point. I know with Progress installs its normally the developers that decide all that stuff as there isn&#8217;t the high need for a DBA that there is in other DBs like MS SQL and Oracle. I think developers really do need to understand the issues of indexing and the likes but having said that, DBA&#8217;s will still be able to do things to improve performance.</p>
<p>Plus there is more and more 3rd party products quering our databases that the orginial developer doesn&#8217;t necessarily have any control over. Things like Crystal, Data ware houses and other BI solutions like <a href="www.easyask.com" rel="nofollow">EasyAsk</a> (a natural language search BI tool for Progress (NB: I work for PRGS)).</p>
<p>Molly</p>
]]></content:encoded>
	</item>
</channel>
</rss>
