588 results found

1. ignore constraint table default

   Separate edit filter rule to ignore constraint names that define a default value for a column

   6 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  ·  Initial Setup  ·  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. Check and Commit Changes over all Databases

   Checking for Changes should be possible over multiple Databases on a Server. All Changes on a Databaseserver should be allowed to commit at once.

   21 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  ·  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. Export / import Link Database configuration setting for shared mode

   It is very hard to do manual database link to repository/SVN if dealing with large number of databases (200 plus within one team) across large number of source control group. Every team member has to spend time and carefully map repository folder.

   One user perform manual link to repository and his/her/ setting validated by QA Team before distributing link config file (xml) to the user group.

   The basic requirement is user should be connected with the DB server and pass the repository path and credential. you may design few screen to navigate and collect user input based on provider input config file that was generated by another user.

   By automating the process of Link and Unlink across the user group to avoid issues/error, saving time, maintain consistency and improve processes etc.

   Let me know if your team need any help for designing this process.

   Thanks!
   Perwez

   It is very hard to do manual database link to repository/SVN if dealing with large number of databases (200 plus within one team) across large number of source control group. Every team member has to spend time and carefully map repository folder.

   One user perform manual link to repository and his/her/ setting validated by QA Team before distributing link config file (xml) to the user group.

   The basic requirement is user should be connected with the DB server and pass the repository path and credential. you may design few screen to navigate and collect user input based on provider input… more

   11 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  ·  Support Additional Source Control Systems  ·  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. Pay attention to case changes in static data tables even if case insensitive collation used

   SQL Source Control will not notice case-only changes to data if the column has a Case Insensitive collation (which is the default out-of-the-box for most SQL Server installations). This bit me when I needed to "sentence case" some "ALL CAPS" data but SQL Source Control didn't even notice until I forced the collation on these columns to be SQLLatin1GeneralCP1CS_AS, which seems unnecessary. Maybe a per-table static data option?

   44 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  ·  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. Changing a data type used in a SP creates problems

   When changing a data type used in a SP (e.g. add a new column to it and commit it). getting latest fails on other linked DBs. You have to drop the SP on the target DB.
   The weird thing is that sometimes it works, but most of the times it doesn't. Not sure why the behavior is not the same all of the times...

   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  ·  Better Support for Shared Db Dev Model  ·  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

6. Enable quick access to the source control log

   Currently accessing the log of the version control system is very slow.
   On a good computer it takes me 20 seconds to open the view history from your menu.

   To open the same log through tortoise svn it takes me 2 seconds to lokate the ex. "Open working base" under the "Under the hood menu" in Setup and 1 second to launch the tortoise SVN log viewer for the project.

   Could you please consider adding a possibility to either open the history quicker, or alternatively allowing the user to open the version control log in an external viewer.

   Maybe there is something that I don't understand here, but I don't see any reason why it should take such along time to open the log..

   I really enjoy your products otherwise:)

   Currently accessing the log of the version control system is very slow.
   On a good computer it takes me 20 seconds to open the view history from your menu.

   To open the same log through tortoise svn it takes me 2 seconds to lokate the ex. "Open working base" under the "Under the hood menu" in Setup and 1 second to launch the tortoise SVN log viewer for the project.

   Could you please consider adding a possibility to either open the history quicker, or alternatively allowing the user to open the version control log in an external viewer.

   Maybe there… 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  ·  History/Log  ·  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

7. Unlinking database from source control takes forever

   When I unlink the database from redgate source contriol SSMS does not respond and it takes more than 10 mins to do.

   6 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  ·  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. Need to disable Source Control.

   Need to disable Source Control. It causes way too many errors and slowness. I only actually need to use it once every 2 weeks when we commit our work, but it runs all the time, and causes a lot of frustration.

   30 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  ·  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. share information about environment between red-gate tools

   SQL Source Control and SQL Prompt may not know about an environment (i.e. a developer not having access to staging or production server) and there's not really a facility in either tool to store information about the version of any environment.

   Thus, SQL Source Control has to ensure backward and forward compatibility when creating migration scripts - which then triggers Code Analysis Errors in SQL Prompt...! It is a mess to clean up, and frankly a waste of time.

   I suggest a feature where I can define my environments in the Tab Coloring in SQL Prompt including a listing of what version things are and then have this information shared around.

   Another possibility is some "future shared utility" where it has useful information that it passes to each tool.

   SQL Source Control and SQL Prompt may not know about an environment (i.e. a developer not having access to staging or production server) and there's not really a facility in either tool to store information about the version of any environment.

   Thus, SQL Source Control has to ensure backward and forward compatibility when creating migration scripts - which then triggers Code Analysis Errors in SQL Prompt...! It is a mess to clean up, and frankly a waste of time.

   I suggest a feature where I can define my environments in the Tab Coloring in SQL Prompt including a listing of… 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  ·  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

10. Upgrade AppData path when installing Upgrade

    I've been told this is by design: When upgrading SQL Source control from say v5 to v6 all of the source control linked db configs are left behind in the previous AppData folder (%localAppData%\Red Gate\ SQL Source Control 5\ in my example) not moved to the new upgrade version folder (%localAppData%\Red Gate\ SQL Source Control 6)

    This leaves a history of folders in every users profile, and for us 'from the beginning' users I've got v3-v6 folders that I shouldn't need.

    I'm told this is for Network and rollback reasons.

    I suggest a checkbox or some such thing during the upgrade process to allow for moving of the link files and other necessary items, into the correct folder. If SC needs it, move it. You could even warn me and say 'these files are 15GB in size and may take some time to move, continue or leave it?'

    I've been told this is by design: When upgrading SQL Source control from say v5 to v6 all of the source control linked db configs are left behind in the previous AppData folder (%localAppData%\Red Gate\ SQL Source Control 5\ in my example) not moved to the new upgrade version folder (%localAppData%\Red Gate\ SQL Source Control 6)

    This leaves a history of folders in every users profile, and for us 'from the beginning' users I've got v3-v6 folders that I shouldn't need.

    I'm told this is for Network and rollback reasons.

    I suggest a checkbox or some such thing during the… 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  ·  History/Log  ·  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

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

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

13. Option to disable object locking from the GUI

    We have found that Source Control object locking can cause severe lag and even instability in SSMS for distant servers. The additional lag affects the SSMS Object Explorer contextual dialogs (right-click). Often the dialog will timeout and fail to render or multiple tries. Although we are able to disable object locking via the RedGateSQLSourceControlEngine_EngineOptions.xml file it would be much nicer to have control from the GUI. This could be in the form of a global on/off switch, or could even add functionality to blacklist certain servers. Alternatively, you could build in some kind of functionality to detect servers with high-latency and automatically turn off object locking.

    We have found that Source Control object locking can cause severe lag and even instability in SSMS for distant servers. The additional lag affects the SSMS Object Explorer contextual dialogs (right-click). Often the dialog will timeout and fail to render or multiple tries. Although we are able to disable object locking via the RedGateSQLSourceControlEngine_EngineOptions.xml file it would be much nicer to have control from the GUI. This could be in the form of a global on/off switch, or could even add functionality to blacklist certain servers. Alternatively, you could build in some kind of functionality to detect servers… 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  ·  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

14. Allow filter rule changes to be undone or a filter to be enabled\disabled

    Changing a filter adds it to the commit tab, but the filter changes cannot be undone - which is a catch 22. If you ever want to undo filters so you can do some manipulation you should be able to undo these changes.

    So, the suggestion is either
    1. Add undo functionality on a filter
    or
    2. Add enable\disable functionality to filter

    I think undo should be there, because once it's in the commit changes tab there is no way out - unless you either unlink and link again or just commit or even worse, put the changes back manually

    12 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  ·  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. Refresh SQLPrompt after get latest

    After running get latest refresh intellisense and sql prompt cache.

    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  ·  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. Stop forcing acceptance of Database Comparison options in Get Latest tab

    Long time user of Redgate Source Control and a really annoying feature is when I'm on the Get Latest tab and there is a change to the Database Comparison options in source control. I can only select the Database Options changes to Get Latest. I cannot opt to get any of the other objects until I 'get' the database options from source control. This is not what is needed. The choice of whether I get the database options should be down to me and I shouldn't be forced to do it. Please make it the same as all other objects in the Get Latest tab and allow myself to make the choice.

    Long time user of Redgate Source Control and a really annoying feature is when I'm on the Get Latest tab and there is a change to the Database Comparison options in source control. I can only select the Database Options changes to Get Latest. I cannot opt to get any of the other objects until I 'get' the database options from source control. This is not what is needed. The choice of whether I get the database options should be down to me and I shouldn't be forced to do it. Please make it the same as all other objects… more

    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…)
    2 comments  ·  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. Allow selection of which SSMS instances to install SQL Source Control

    Given the size of our databases, SQL Source Control is VERY slow, frequently locking up SSMS for a minute or more.

    As a result I'd like to (say) use SSMS 2014 for SQL Source Control, leaving SSMS 2017 free to work with.

    Could we please have the option of choosing which SSMS instances to install it against?

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

19. SQL Source Control - Filter

    We are a shop that have multiple systems for clients that we managed from within a single database, using a separate Schema for each system.

    I would like to be able to link a TFS database to a filtered list of objects (preferably) an entire schema but I could see where others might like just a subset of other objects.

    If this is currently possible please let me know but I do not see a way to accomplish this without having a separate database for each system per client.

    14 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  ·  Better Support for Shared Db Dev Model  ·  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
    started  ·  AdminStephanie (Product Manager, Redgate) responded

    This is possible using filters.

20. migration scripts

    When re-linking databases to source control, there is a warning message about loosing all uncommitted migration scripts, with only a OK/Cancel option. It's seems there should be an option for 'take me to the commit page' so that I can commit those scripts, then re-link.

    2 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  ·  Better Support for Shared Db Dev Model  ·  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