blogs.conchango.com

welcome to the conchango blogging site
Welcome to blogs.conchango.com Sign in | Join | Help
in Search
Blogs

SSIS Junkie

Datadude/DBPro/VSTS4DBP/huh...???

It has annoyed me for a long time that this product (note I'm linking to it, not naming it) suffers from a lack of identity. The official name is "Visual Studio 2005 Team Edition for Database Professionals" (58 characters for pity's sake) though in some places it is listed as "Visual Studio 2005 Team Edition for Database Professionals" and variants thereof. Whatever...it is a ridiculous name; its far too wordy. As such most people resort to abbreviating it to "DBPro" or assuming its more colloquial name "datadude".

Thankfully (!!!) the Visual Studio peeps have realised the folly of their choice of nomenclature and have put a stake in the ground by announcing that from hereon it will have a new name. Unfortunately its only slightly less wordy at "Visual Studio Team System 2008 Database Edition" which rolls in at a measly 47 characters. Colloquially they want it known as "Database Edition" but I daresay that "datadude" will still proliferate.

Thanks to Cameron for the tip.

-Jamie

 

 

Published 24 August 2007 21:40 by jamie.thomson

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

twh said:

I think this edition of VS is a product in search of an audience.  The DBAs I know all concern themselves with the SQL Service, disk space, backups, database availability, overall server performance, etc.  They don't design tables, views and stored procedures.  The application developers do that.  (Maybe I just have never worked in a large enough shop where the roles were that granular).  Are developers supposed to have and use two editions of Visual Studio?  The features in the database edition should just be rolled into the software developer edition.

August 30, 2007 15:02
 

jamie.thomson said:

twh,

Sorry, I have to disagree with you on that one. Database design is a specialized role - ordinarily I wouldn't want "developers" (I presume you mean people that write code in the middle and upper tier) designing the data model. I'd want my data architect doing it.

However, a data architect first has to work at the logical data model level and there is nothing in the tool to support that. The tool does seem to cross a few role boundaries I agree. Having said that I've used it extensively since it was in beta and I love it. It makes my job SO much easier.

-Jamie

August 30, 2007 16:06
 

blindman said:

This DBA concerns himself primarily with database design and sql coding, and I have to say that datadude sucks.  By any conservative estimate, between 25 and 50 percent of the hours on our current project have been eaten up by synchronization issues with this product.  And now, three weeks past our product release data, I find that critical code and schema changes I implemented months ago have never been merged into the testing and production environments.

The whole idea behind datadude, that schema and code changes can be rolled out independent of eachother, is a flawed concept and dooms this tool to failure.

December 7, 2007 21:31

Leave a Comment

(required) 
(optional)
(required) 
Submit

This Blog

Syndication

News
© 2008 - Any comments or statements made herein do not necessarily reflect those of Conchango.
Powered by Community Server (Personal Edition), by Telligent Systems