50 results found

1. Tabular visualization of static data differences between database and repository

   A tabular visualization with the differentiation between "added" (only in database), "changed" (on both sides existing but with different data) and "removed" (only in repository) would help to check the differences and with a possibility to select certain differences which should be committed, it would also be more efficient that different developers can commit only their own changes on a table, which is linked regarding static data.
   In addition a possibility to hide the unchanged columns in the tabular visualization would also be really good.

   •  

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Static Data  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Add ability to Merge Static Data

   "Take theirs" and "Keep mine" are an all or nothing option, I would like to have more control over this and be able to keep my new records but take the updated, or keep my updated records but take the new records, for example.

   19 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Static Data  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Make static data UI sortable / searchable

   With 100s or 1000s of tables it becomes quite tricky to find objects in the static data link / unlink UI. Therefore, I suggest adding a search textbox there as well as making the UI columns (name, key, schema) sortable.

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Static Data  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Display summary of Static Data differences

   When displaying the Static Data differences in SQL Source Control it would be very useful to show the number of records that are Different/Identical/In Database Only/In Source Control Only.

   When tables have thousands of records it can be difficult to know the scale of what you’re about to check in or get by just scrolling down a long list. A tab displaying the records for each distinct group would be even better.

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Static Data  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Include sys.message custom messages in static data

   The deprecated RAISERROR, and newer THROW T-SQL instructions can use custom (user-defined) messages written into the sys.messages table using sp_addmessage.
   Since these are part of the "source" of a database in SQL Server, and should be syncronised across developers and implemented in production, it would be nice if the custom messages saved in this table can also be added to the static data in a repository.

   5 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Static Data  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Allow a pre and post scrip to run on SQL Data Compare

   Sometimes I need to write scripts to run before and after a SQL Data Compare.

   13 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Static Data  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Commandline Source control

   It would be great if we could integrate SQL Source Control with our build scripts. For example a simple command line command to get the latest changes and apply (or script) them to our staging environment would be great. Or a command to commit all changes to source control.

   5 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Static Data  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Source Control Migration Scripts - Ability to add before or after main block

   Presently a standalone migration script runs before the main block. This seems odd as the point is to migrate data and for that you need schema to be in place.

   I would like to be able to add standalone migration scripts to the end of the main block.

   We ship databases with some data populated. (This is not simple static data that can be managed using linked tables). We ship for example some out the box entities such as Roles, A base User, a base Organization etc. They have circular references so to insert we have to turn off table constraints, add the data and re-enable. It would be great if we could add the script to do this to the end of the migration block rather than to an object at check in.

   I propose you type Migration scripts:

   1 Schema Migration - you have this whereby it is tied to say a table update
   2. Pre Action Migration - executes before any main part of the checkout
   3. Post Action Migration - executes after the main checkout block

   The inability to do this is causing quite a bit of cussing on Forums.

   Regards

   Phil

   Presently a standalone migration script runs before the main block. This seems odd as the point is to migrate data and for that you need schema to be in place.

   I would like to be able to add standalone migration scripts to the end of the main block.

   We ship databases with some data populated. (This is not simple static data that can be managed using linked tables). We ship for example some out the box entities such as Roles, A base User, a base Organization etc. They have circular references so to insert we have to turn off table… more

   10 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Static Data  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. 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

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Static Data  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Add a "Check Static Data" now button to the "Get Latest" tab when auto-check of static data is unselected

    We have a rather large schema with numerous static data linked...
    When I turn off the automatic check of static data, the Get Latest and commit refresh operations take only seconds!! (Awesome!)
    When i turn ON auto check of static data, it takes almost a minute (yawn!).

    It would be really great if I could have the best of both worlds... Do not automatically check static data, but manually check it as I see fit with a separate button on the GetLatest tab that says "check static data now" or something.

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Allow SQL Source Control to visualize static data potentially hidden by Row-Level Security

    While comparing static data in SQL Compare, there might occur a "red herring" issue where SQL Source Control cannot see filtered table-data due to being read by a user unprivileged for Row-Level Security. Since SQL Source Control cannot see the table-data, it will then suggest to either

    a) Fetch all table-data from the linked repository (causing all kinds of PK- and other constraint issues)
    or
    b) Commit the deletion of all table-data to the linked repository

    We don't want to do either of these actions. Although bypassing Row-Level Security for an unprivileged user isn't possible, it is still possible for an unprivileged user to see the row-count and physical index-stats of a table both by querying system-tables and viewing the "Properties" page of a table. By doing this, it is technically possible for SQL Source Control to see if the rowcount of the table matches the rowcount found in the system-tables and, if they differ, provide a clear warning in the comparison window that this particular table is subject to Row-Level Security and that rows may be hidden to the user.

    While comparing static data in SQL Compare, there might occur a "red herring" issue where SQL Source Control cannot see filtered table-data due to being read by a user unprivileged for Row-Level Security. Since SQL Source Control cannot see the table-data, it will then suggest to either

    a) Fetch all table-data from the linked repository (causing all kinds of PK- and other constraint issues)
    or
    b) Commit the deletion of all table-data to the linked repository

    We don't want to do either of these actions. Although bypassing Row-Level Security for an unprivileged user isn't possible, it is still possible for… more

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. 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 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    6 comments  ·  Static Data  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    under review  ·  Kendra responded

    Hi 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 variables in migration and post-deployment scripts

    If there are other use cases where a migrations approach would add value to the team – such as easily being able to run data modification statements as part of deployments, or being able to customize the TSQL for schema changes – then changing from SQL Source Control to SQL Change Automation makes sense.

    Hi 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… more

13. 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

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. 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+key

    I 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 feature so that is gets attention.

    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+key

    I 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… more

    83 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Static Data  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Keeps detecting changes for value s'

    Hello,
    I have a table with only one PK column of type nvarchar(200) which contains static data.
    Source Control keeps telling that there are changes even after saving the changes. It seems that it has some issues with the value s'

    Database version:
    -- Only In Database

    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N's''')

    -- Identical

    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N'a')
    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N'aan')
    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N'aan de')

    Latest source control version:
    -- Only In Source Control

    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N's''')
    -- Identical

    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N'a')
    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N'aan')
    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N'aan de')

    I'm using version 5.6.0.5731

    Hello,
    I have a table with only one PK column of type nvarchar(200) which contains static data.
    Source Control keeps telling that there are changes even after saving the changes. It seems that it has some issues with the value s'

    Database version:
    -- Only In Database

    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N's''')

    -- Identical

    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N'a')
    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N'aan')
    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N'aan de')

    Latest source control version:
    -- Only In Source Control

    INSERT INTO [dbo].[tab54Voorvoegsels] ([Voorvoegsel]) VALUES (N's''')
    --… more

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Hide columns for System Version Tables

    We are using System Versioned Tables, and on these tables SQL server adds 2 new columns SysStartTime and SysEndTime. These columns are typically marked as hidden and we need a way to ignore comparison for these. Either by a column level filter, or an option to ignore system versioning columns

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. I would like to be able to pause scanning a database for changes. It is trying to do 3 at the same time with on being really.

    I would like to be able to pause/start scanning a database for changes as will. It is trying to do several at the same time right now and one of them is huge which is taking longer than it should. If I could only scan the one I am working with at the moment it would save me time system resources.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Exporting Multiple Tables from the results pane to seperate Excel Tabs

    The open in excel feature is impressive and I love to use it for ad-hoc extracts. Having the ability to extract multiple results in 1 go to a single Excel file with different sheets would be great.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Support unicode characters in data scripts Arabic for example

    When linking static data to source control the unicode characters are appearing as question marks
    so please add the support for the unicode characters in the script files

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. SQL Source Control Static Views (or Table Subsets using WHERE clause)

    I would like the ability to source control a subset of a table (perhaps using a view).

    I have inherited a database where lookup data is intermixed with user defined data. We reference the lookup data in the table using a code (VARCHAR) that is unique when another field is NULL, so it is possible to ensure that records are created/updated/deleted without concern for the primary key involved.

    For more information, you can refer to this forum post:
    http://www.red-gate.com/messageboard/viewtopic.php?p=50087

    636 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    30 comments  ·  Static Data  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    under review  ·  Kendra responded

    Hi everyone. I have merged some User Voice items on this topic of “filtered” static data, as there was significant overlap. I want to share our current guidance on handling scenarios where you need to version a subset of the columns and/or rows in the table.

    With SQL Source control, the best option at this point is to use a post-deployment script for this purpose.

    SQL Source Control introduced pre- and post- scripts in v6.3.

    A post-deployment script gives you a good amount of flexibility over exactly which rows or columns of data you want to include in your project. Example post-deployment scripts for static data are 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 variables in migration and post-deployment scripts

    If there are other use cases where a migrations approach would add value to the team – such as easily being able to run data modification statements as part of deployments, or being able to customize the TSQL for schema changes – then changing from SQL Source Control to SQL Change Automation might make sense.

    Hi everyone. I have merged some User Voice items on this topic of “filtered” static data, as there was significant overlap. I want to share our current guidance on handling scenarios where you need to version a subset of the columns and/or rows in the table.

    With SQL Source control, the best option at this point is to use a post-deployment script for this purpose.

    SQL Source Control introduced pre- and post- scripts in v6.3.

    A post-deployment script gives you a good amount of flexibility over exactly which rows or columns of data you want to include in your project. Example post-deployment scripts for static data are 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… more