50 results found
-
Show number of rows and columns when adding static data
When adding static data from a large system it would be wonderful to be able to sort on a column stating how many rows the table contains!
3 votes -
some extended property or search item or project option to “link” static data tables ONLY – this would be a huge time saver.
We have thousands of tables (some with millions of rows) with only 90-100 static data tables.
At the moment, I have to edit the project; untick all then tick 90-100 manually which is very time consuming.
If there was some extended property or search item or project option to “link” static data tables ONLY – this would be a huge time saver.
Thanks for your response.
Regards
11 votes -
Change the icon in ssms for the tables that are linked as static data.
When you link a table as static data in Sql Source control it would be nice if the static tables were easily identifiable under the tables node in management studio.
28 votes -
Increase performance of SQL Source Control when using Static Data. Even with small amount of static data the performace is simply not accep
Increase performance of SQL Source Control when using Static Data. Even with small amount of static data the performace of the tool is not acceptable.
24 votes -
Changes to data in Static Data Linked Tables should be included in the Migration Script, just as changes to the schema are.
If a table is linked as static data, any changes to the data should automatically be included in the migration script, just as changes to the schema are. Having to write a manual script or use the separate compare tool is extra work, and small changes are easy to miss.
43 votes -
Custom comparison key in SQL Source Control
When adding a static table to be managed by SSC the comparison key is automatically selected. Our tables have auto generated INT ID columns as PK used in FK's. In our Static Data tables we have other columns that are unique and for them we have UK’s that we would like to use as the comparison key.
Here is another with the same issue...
http://www.red-gate.com/messageboard/viewtopic.php?t=16498&highlight=comparison+keyI have not found any workaround for this yet at least.
I believe that this would be a great improvement for SSC and would be used by many. If you agree please vote for this…83 votes -
Support different static data per customer
I have a single schema for all customers but different reference data for different customers. It would be nice if I could manage this all within SQL Source Control. This should also be understood by SQL Compare and my continuous integration system when it comes time to deploy this to my different environments and customers' sites.
254 votesHi all. Thank you for your votes and feedback on this issue over the years. Here is our current guidance for this suggestion:
Post-deployment scripts give you flexibility for static data
With SQL Source Control, you can now use a post-deployment script to “dynamically” deploy static data based on a factor such as @@SERVERNAME or other query-able conditions.
SQL Source Control introduced pre- and post- scripts in v6.3.
An example post-deployment script which shows how to control deployment of static data by environment is here: https://documentation.red-gate.com/soc7/common-tasks/working-with-pre-post-deployment-scripts/static-data
If you make heavy use of Static Data, we have stronger support for this in SQL Change Automation.
SQL Change Automation:
- Supports column filtered static data tables in the SCA plugin in SSMS
Supports multiple post-deployment scripts, in case there is a preference to manage static data tables in dedicated post-deployment scripts - Allows approaches like bulk loading larger static data tables by supporting SQLCMD…
- Supports column filtered static data tables in the SCA plugin in SSMS
-
When tables with linked data are renamed, the new tables do not have linked data
Linked data settings should be remembered when a table is renamed
1 vote -
SQL Source Control Configuring Data Compare Options
Make it possible for us to configure how SQL Source Control does its data compare. There are some great settings that work within SQL Data Compare 10 that allow a user to configure how data in each table is compared between data sources. Currently the main feature I want is to allow the selection of table columns to actually compare (i.e. one column is an identity field which isn't always the same).
34 votes -
Linked data rollback does not filter table(s) when using Sql Data Compare
A developer changed a value on some static reference data. I right-clicked on the table to show the source control history. Then I selected the latest changeset to overwrite changes made to the database. This task uses Data Compare. However, when the tool comes up, all of the tables are selected instead of the one that I selected. I wanted Sql Source Control to filter just the table that I selected or at least filter the tables associated with a targeted changeset.
1 vote -
Bug with certain tables names
If you have 2 tables Config and ConfigData and wish to store static data for both of them then after you have committed successfully it comes back saying that that the Config is not committed and lets you commit it again. Each time incrementing the committed version but always saying there is a difference. It is most liely because you store the data scripts as <tablename>_data.sql and it is getting confused between the 2 tables.
1 vote -
1 vote
-
Bug. The Change Connection functionality within the SQL Editor is disabled by SQL Source Control.
When my connection is disabled in SSMS, I use the Change Connection functionality to reestablish it. With SQL Source Control installed, I can't because the Change Connection functionality is disabled.
1 vote -
Link/Unlink Static Data - change to non-modal dialog
I am trying to pick my tables for the static data feature I just dound and i'm using "explore data" to find the table I want to store the data for. The popup however is modal so I cant scroll the data explorer without saving the ones I just ticked.
11 votes -
Allow SQL source control to cascade deletes when the database does not have cascading deletes enabled.
When we hop back in our source control repository to an older release and "update" our database, occasionally there is new static data that is referenced by non-static entries in the database. We do not have cascading deletes enabled for various reasons outside of the developers control, but in this particular instance it causes errors when static data is removed from the database to revert to an older version. Would it be possible to have redgate check incoming foreign keys and generate all the necessary deletes to allow static data removal?
3 votes -
updated data on static tables
Disable Foreig Keys of table of transaction
1 vote -
DataLink
Just view the tables checked as static.
Comes in handy when comparing to other Databases (hence same database but for instance on another level -> DEV-TST-ACC-PRD)1 vote -
Commit data and schema changes separetly
A table is under source control and the data of that table is linked as static data.
Both table definition and data has been changed and are visible in the 'Commit changes' tab.
Since the data is just edited and changed for development purpose it should not be committed.
But in this situation it is impossible to only commit de table definition.
When checking the table the data is also checked (and the other way around also).It would be nice to be able to commit the changes separetly.
20 votes -
static data, Bulk insert for get latest
Do not use transactions but use bulk insert in order to reduce the get latest time. A 'flush and refill' approach using bulk insert should be faster in hours with 10K plus records.
A two processor, dual core computer with 8GB of RAM and a Windows experience index of 6.5 takes over 8 hours to get lates on 50K records.
10 votesThanks for this feedback and for the votes for this suggestion.
For users who need to manage larger volumes of static data, we currently recommend versioning the database with SQL Change Automation. SQL Change Automation has stronger support for static data:
- Supports column filtered static data tables in the SCA plugin in SSMS
- Supports multiple post-deployment scripts, in case there is a preference to manage static data tables in dedicated post-deployment scripts
- Allows approaches like bulk loading larger static data tables by supporting SQLCMD variables in migration and post-deployment scripts
I do understand that you are looking for this feature in SQL Source Control, but wanted to surface this option for other readers who may be interested in either tool.
-
Export the list of static data linked
Whe you have a multi branched dababase environment could be helpful to export from the main database the list of tables linked (in xml ie, or json, as you wish), in order to reload it on the branch database. Obviously only for the objects that exist. An alternative could be to save to "other similar database" too..
7 votes
- Don't see your idea?