these are 2 idéea:

any kind of default connexion. Choosing a target connexion every action is tedious and dangerous: when I generated new data first time, I dumped everything into a prod database!

some support to mke scriptable deploiement of a dbpro project

thank you

I think I speak for everyone when I say that the design-time experience needs significant improvement. Use the VS2005 class designer stuff to make designing tables similar. Get rid of the gray blocky crap and make it sexy. Just because it's the lowly DB doesn't mean it has to be ugly as sin.

1. DBPro is currently schema aware. Make it data aware as well (this has been discussed at length on the MSDN forum and connect postings have gone in so no point boring anyone with it here)

2. Intellisense.

-Jamie

Dans l'attente de la sortie toujours pas annoncé… Sur le blog official on retrouve juste ce petit commentaire…

Optionally be able to save the configurations of schema and data compare.

Optionally be able to add schema and data compare configurations into the project.  (As data generation is now)

Programatic access to higher level API's (table level, schema level) for data generation.

NON random lookup data generation based on fixed data ("external" scripts and / or data lookup)

In order to bring DataDude into line with the rest of the Team Editions (and facilitate VS Pro editing out of TFS or VSS) make the Data Tools the Team Edition functionality / feature set and allow the basic functionality (schema design, editing, source control)  in all versions of VS starting with VS Pro.

DataDude has already helped me a lot in it's various CTP releases. It's a great product. But in my opinion there is still a lot missing... My personal favorites list:

 1a) Visual Designers for Tables

 1b) ERD like SQL Server Workbench

 2) Intellisense

 3) Improved speed in large projects (many hundreds of tables and thousands of keys and stored procedures)

 4) Timestamp fields should not be considered (or only optionally considered) when comparing data

 5) Make generated scripts better compatible with SSIS (of SQL Server 2005)

I have to second gnschenker's comments.  Especially intellisense and ERD capability - while DB Pro is a huge achievement, the productivity gained from visual modeling sync-to scripts is critical for cost/benefit