50 results found
-
Functionality after restore from command
After we have run a restore database command, the source control do not notice, that some, earlier loaded stored procedures from lastest version are after that newly out of date.
Source countrol should recognize a restore and scan completely new for the latest changes.4 votes -
5 votes
-
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 -
Make SQL Data Easier to Merge (Static Data)
Currently, SQL Data files contain a bunch of insert statements, but the order of the insert statements can be inconsistent. For example, new records might get inserted on the top or the bottom. Also, multiple SET IDENTITYINSERT statements sometimes get created. This makes it difficuly to merge data changes between multiple branches in TFS Source Control. If the Insert statements had a consistent order and only included one SET IDENTITYINSERT diffs and merges would be easier.
530 votesThanks for this suggestion and for the many comments and upvotes. I realize that this is a pain point.
I have a few shorter-term workarounds to summarize as well as some information on the longer roadmap in this update. I know these shorter-term workarounds aren’t perfect (I summarize the pros and cons), but I’m posting them as they may help a few folks.
Workaround 1) When data changes to static data need to be made, use a “relink the table” pattern
One can “cleanly rescript” a static data table in SQL Source Control by:- Unlinking the static data table
- Committing
- Relinking the static data table
- Committing
Pro: This works with the GUI and requires no special knowledge or comfort with TSQL. This may help folks with just a few static data tables.
Con: This requires extra steps and results in extra commits in the history, which I realize can… -
Foreign keys recreated with NOCHECK during data sync
We have the same issue as noted here: http://www.red-gate.com/messageboard/viewtopic.php?t=13662&highlight=foriegn+foreign+key
The FK is recreated with NOCHECK during data sync which triggers a schema change.
104 votes -
Warn when adding static data tables that have foreign keys
When adding a static data table to source control, there should be a warning if that table has a foreign key constraint on another table and give the option to include that table as static data also. As it is the error you get in SQLCI is quite hard to decipher when SQL Source Control is used in conjuction with SQLCI.
3 votes -
Removing column does not generate update in static data
If a table is setup for static data, and you remove one or more columns from that table, the static data is not updated in the working directory when "Saving changes".
7 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 -
allow copy names from result Cell by Cell
allow copy names from result Cell by Cell
Like if we want to copy only object name it should allow.3 votes -
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 -
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 -
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 -
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 -
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. 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 -
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
-
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 -
updated data on static tables
Disable Foreig Keys of table of transaction
1 vote -
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
- Don't see your idea?