<?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>Paul Nielsen : Team System for DB Professionals</title><link>http://sqlblog.com/blogs/paul_nielsen/archive/tags/Team+System+for+DB+Professionals/default.aspx</link><description>Tags: Team System for DB Professionals</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>My Biggest SQL Server Pet Peeves</title><link>http://sqlblog.com/blogs/paul_nielsen/archive/2007/04/02/my-biggest-sql-server-pet-peeves.aspx</link><pubDate>Mon, 02 Apr 2007 20:25:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:1075</guid><dc:creator>Paul Nielsen</dc:creator><slash:comments>15</slash:comments><comments>http://sqlblog.com/blogs/paul_nielsen/comments/1075.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/paul_nielsen/commentrss.aspx?PostID=1075</wfw:commentRss><description>&lt;P class=MsoListParagraphCxSpFirst style="MARGIN:0in 0in 0pt 0.5in;TEXT-INDENT:-0.25in;mso-list:l0 level1 lfo1;"&gt;&lt;SPAN style="mso-bidi-font-family:Calibri;mso-bidi-theme-font:minor-latin;"&gt;&lt;SPAN style="mso-list:Ignore;"&gt;&lt;FONT face=Calibri size=3&gt;1)&lt;/FONT&gt;&lt;SPAN style="FONT:7pt 'Times New Roman';"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;FONT face=Calibri size=3&gt;Team System for DB Professionals runs only in Visual Studio. &lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoListParagraphCxSpLast style="MARGIN:0in 0in 10pt 0.5in;TEXT-INDENT:-0.25in;mso-list:l0 level1 lfo1;"&gt;&lt;SPAN style="mso-bidi-font-family:Calibri;mso-bidi-theme-font:minor-latin;"&gt;&lt;SPAN style="mso-list:Ignore;"&gt;&lt;FONT face=Calibri size=3&gt;2)&lt;/FONT&gt;&lt;SPAN style="FONT:7pt 'Times New Roman';"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;FONT face=Calibri size=3&gt;Stored Procedure Debugging is only available in Visual Studio&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;Both of these facts bother me because together they point to a trend to move database development from the database professional to the application developer. &lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT size=3&gt;&lt;FONT face=Calibri&gt;The primary tool of the SQL Server database professional&amp;nbsp;is Management Studio and the primary language of SQL Server database development is T-SQL. For these two reasons, both stored procedure debugging and Data Dude belong in Management Studio first and Visual Studio only as a secondary option. &lt;SPAN style="mso-spacerun:yes;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;When I teach a SQL Server upgrade class, the students are shocked to learn that store procedure debugging was moved from the database tool to Visual Studio. Most SQL Server professionals I know don’t even have Visual Studio installed on their workstation. &lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN:0in 0in 10pt;"&gt;&lt;FONT face=Calibri size=3&gt;Microsoft, please respect the database professional and make the common sense move to place database tools inside the primary environment first.&lt;/FONT&gt;&lt;/P&gt;&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=1075" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/paul_nielsen/archive/tags/Team+System+for+DB+Professionals/default.aspx">Team System for DB Professionals</category><category domain="http://sqlblog.com/blogs/paul_nielsen/archive/tags/Debugging/default.aspx">Debugging</category></item></channel></rss>