Feature request: WHERE clause when linking static data

A SQL Server Management Studio add-in to source control your database in Subversion or Team Foundation Server.

Moderators: Chris Auckland, David Atkinson, sherr, PhilScrace

Feature request: WHERE clause when linking static data

Postby Kasper Bengtsen » Thu Sep 15, 2011 10:39 am

SQL Source Control can be used as the tool for implementing continuous integration of the database schema (using the command line tool for SQL Compare to compare the source control repository vs. the integration database).
However SQL Source Control will not be entirely useful in doing the same on the data side, as long as a WHERE clause cannot be assigned to the linking of static data (it is possible to assign one in the SQL Data Compare tool, but developers don't generally need access to that).

Including this feature will (in our case anyway) make it possible to go "full circle" in using RedGate tools for continuous integration of the database schema and data.

Example.: Only some reference data in a DocumentTemplate table needs to go into the integration database, not the 100.000 test data rows created by the developers. :) Translating into, for example "WHERE DocumentType = 1" or something of that kind.
Kasper Bengtsen
 
Posts: 6
Joined: Wed Jul 13, 2011 1:14 pm

Postby eddie davis » Mon Sep 19, 2011 10:39 am

Thank you for your post into the forum.

I have submitted this feature request on your behalf. The reference number for the feature request submitted is SOC-3054.

I cannot guarantee the success of the request submitted. Or if approval is given, what future version of the product it will appear in.

Many Thanks
Eddie
Eddie Davis
Technical Support Engineer
Red Gate Software Ltd
E-mail: support@red-gate.com
eddie davis
 
Posts: 943
Joined: Wed Jun 14, 2006 3:47 pm
Location: Red Gate Software

Postby David Atkinson » Mon Sep 19, 2011 11:45 am

Kasper,

We do hope to add this feature at some point in a later version. In the meantime please just set the static data tables in SQL Source Control to be those tables that *exclusively* have static data. For those which have a mix, manage these outside of the tool.

Apologies for the inconvenience.

David Atkinson
Product Manager
Red Gate Software
David Atkinson
 
Posts: 1124
Joined: Mon Dec 05, 2005 4:54 pm
Location: Twitter: @dtabase

Postby Kasper Bengtsen » Fri Sep 30, 2011 12:08 pm

Thanks for the quick reply

Sounds great :D

The improvements in the source control plugin (like the latest option to filter out objects) is really helpful in implementing continuous integration without having to do too many manual tasks.

Implementing this feature request will eliminate another one of those tasks. :)
Kasper Bengtsen
 
Posts: 6
Joined: Wed Jul 13, 2011 1:14 pm

Postby David Atkinson » Fri Sep 30, 2011 1:14 pm

Yes, we're really focusing on building a strong continuous integration story. At the moment you may have noticed that the filter options you set up in SQL Source Control aren't picked up by SQL Compare. This will be fixed in the EA build due out next week.

And of course the ability to add custom change scripts with the upcoming migrations feature will further strengthen continuous integration.

David
David Atkinson
 
Posts: 1124
Joined: Mon Dec 05, 2005 4:54 pm
Location: Twitter: @dtabase


Return to SQL Source Control 2

Who is online

Users browsing this forum: No registered users and 0 guests