588 results found

1. Remove the Non-Standard filegroups warning

   When you create an object on a file gorup other than primary you get a warning message that you are using non-standard filegroups.

   This can be a little confusing since, in most cases the filegroups were crated and applied to objects for a specific purpose.

   Potentially replace with a warning that the non DEFAULT filegroup being used

   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

2. Indexed view definitions don't compare with latest version properly

   When comparing view definitions from local objects to latest source control version (perforce in our case), SQL Source control doesn't properly read the data compression options from the source control version. So we'll get a difference, showing "WITH (DATA_COMPRESSION = PAGE)" highlighted orange on the left....however the source control file also has this clause, it's just not being read properly. If I check in the file, it will refresh and the same object will still show a difference with source control, even though it's not.

   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  ·  History/Log  ·  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. Allow ability to ignore specified object(s) by database

   Most objects are shared among our several databases, while some only apply to some (or only one) of our databases. Add the ability to ignore objects by database by right-clicking the database object and clicking a menu item like "Ignore this object in this database" and/or "Ignore this object in all databases except this database". So then we don't need to have an object in one/many of of our databases that is not used in that database(s), source control would not show the need to be updated or added because it is on the ignore list for that database.

   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  ·  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. Amending last commit

   We use SQL source control linked to Gerrit. It would be really useful to be able to 'Amend last Commit' inside the GUI.

   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

5. Use case-sensitive object definition

   Better support for the "Use case-sensitive object definition". Especially for changes in columns that are used in foreign keys. Now it is possible to commit changes such that the "Use case-sensitive object definition" cannot be used anymore.

   1. Link the database to source control with “Use case-sensitive object definition” turned off (which seems to be default?)
   2. Create two tables, one with a foreign key referencing the other table.
   3. Save these tables to the working folder
   4. Alter the case of the field referenced by the foreign key and alter something else on the same table too. That way the change in case will show up in the “Commit changes” tab. Save the changes to the working folder.
   5. Turn on the “Use case-sensitive object definition” setting
   6. Switch to the “Commit changes” -> error

   Better support for the "Use case-sensitive object definition". Especially for changes in columns that are used in foreign keys. Now it is possible to commit changes such that the "Use case-sensitive object definition" cannot be used anymore.

   1. Link the database to source control with “Use case-sensitive object definition” turned off (which seems to be default?)
   2. Create two tables, one with a foreign key referencing the other table.
   3. Save these tables to the working folder
   4. Alter the case of the field referenced by the foreign key and alter something else on the same table too. That way the change in case… 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…)
   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

6. When a user closes a session/SSMS it would be useful to have the user to prompted about any pending check-ins (shared db).

   We use a shared environment, and if someone forgets to check something in, then the changes made appear as if from the next user to edit the item.

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

7. The ability to filter by change type, object name, type, owner, etc in addition to the default of showing all changed object
   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  ·  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

8. For 'Commit changes' the button to refresh is on the far right. For 'Get latest' the button is on the far left side of the window.

   Consistency is king. Having the buttons always at the same place makes it easier. So, either you have both refresh buttons on the far right or on the far left side of the window. I personally prefer the left side as this is closer to the tabs. But that's just me.

   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

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

   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

10. I just installed a "minor update". If it is minor, why are you prompting me to read a 19 page, 7,500 word licence agreement?

    Only display changes to the agreement and stop wasting my time.

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

11. Screen Reader Access

    Can you make the tools more accessible through screen reader?
    The Tools are not readily accessible through Screen Readers and thus are very difficult to use by partial sighted people who rely on screen readers. I am one of them.

    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

12. Allow sorting Commit Changes by multiple columns (e.g. Type then Name)

    I would like the option of sorting by more than one column at a time in Commit Changes. I typically want to sort first by Type and then by Object name.

    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

13. Embed Coments

    You should consider adding tokens like the following:

    --%version --%
    --%modifications --%

    When you check out the latest version of a SQL Script, Source contral would replace a token in the script with the version history from the repository.
    When the script is checked it additions made in the modifications token are grabbed and included in the comments box for check-in.

    In addition the modification comments could be formatted a little better either by discreet fields or by a masked format.
    Make the message concise and informative. I use the following format:

    [bug/issue number] [Area of Focus] [Action completed]

    Ticket: 199112 Datamart - Updated spCustomer to filter for zipcode

    Reference to tracking systems

    More detailed information is always necessary. Referencing your commit to issue tracking system not only a good idea, but cuts down on the amount of information you need to include in your commit message.

    Area of Focus Label

    Culling through a massive list of commit messages is hard enough, providing a focus area to filter your commits makes things easier. Determining what labels to employ is subjective, but having them saves a lot of time.

    Action completed

    I use the elevator pitch technique when describing the action completed. Imagine getting into an elevator and having to describe the code you are committing to repository in the fewest words possible without using technical jargon.

    Perhaps -- # would be a better token, whereas % could trip up some XML parsers.

    Examples:
    -- #author Jim Smith
    -- #version 1.1
    -- #desc Listing of customer addresses
    -- #mod #author Frank Jones - #Comment

    You should consider adding tokens like the following:

    --%version --%
    --%modifications --%

    When you check out the latest version of a SQL Script, Source contral would replace a token in the script with the version history from the repository.
    When the script is checked it additions made in the modifications token are grabbed and included in the comments box for check-in.

    In addition the modification comments could be formatted a little better either by discreet fields or by a masked format.
    Make the message concise and informative. I use the following format:

    [bug/issue number] [Area of Focus] [Action completed]

    Ticket:… 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…)
    0 comments  ·  History/Log  ·  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. Strangely "Last changed by" is incorrect.

    I modified 10+ tables by dropping and creating an index. On two tables the index didn't exist and I had to create it. Big was my surprise that those two tables had a different user than me set as the owner of the change. It is even more strange that each table has a different user mentioned as the change owner.

    No big issue, but still something weird. And perhaps better if the change is linked to the user doing the change.

    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  ·  History/Log  ·  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. Using Powershell to generate/checkin Migration Scripts for each changeset/commit

    We are unable to use SQL Compare to deploy Migration Scripts to all of our environments and simultaneously maintain commit level control over what does or does not get deployed to each environment for each release, especially with the high volume of changes and the number of last minute changes to release choices in the final stages of release planning. The amount of manual review of the final deployment script is unsustainable.

    Using Powershell, we would like to auto-generate Migration Scripts for each Commit/ChangeSet and Commit those Migration Scripts to TFS. This would allow us to modify the content of the scripts for each environment and to decide what scripts to apply as appropriately as possible for each environment, using a system that allows a repeatable and sequenced deployment order (also coordinated by Powershell/Octopus).

    Instead of using the RGSSC’s UI to create Migrations Scripts for each Commit, we would like to use PowerShell to create the Migration Scripts for all Commits, and use Powershell to check those Migration Scripts in.

    We are unable to use SQL Compare to deploy Migration Scripts to all of our environments and simultaneously maintain commit level control over what does or does not get deployed to each environment for each release, especially with the high volume of changes and the number of last minute changes to release choices in the final stages of release planning. The amount of manual review of the final deployment script is unsustainable.

    Using Powershell, we would like to auto-generate Migration Scripts for each Commit/ChangeSet and Commit those Migration Scripts to TFS. This would allow us to modify the content of… 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…)
    1 comment  ·  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

16. Let me use the old system of committing first and then generating a script

    From the commit dialog I can see the changes that have occurred and decide whether to commit or not. Then after committing I could generate a script covering those amendments. It appears that you have removed this functionality. Now under Migrations I just get a list of objects with changes and have no idea what has changed and just have to blindly generate a migration script or flick back and forth between the Commit tab and Migrations tab to determine what to include.
    Maybe I have missed something - only been trying for a day!

    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…)
    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

17. Add a "rerun" option for edited migration scripts

    Currently there is an option to edit migration scripts however edits will not get applied to other environments if the old version of the script was already run.

    Imagine the scenario where a migration script is created to update one record in a table that does not have it's data versioned. The script is checked in and deployed to the CI environment and the QA (test) environment. QA test finds that the update was incorrect. Development edits the migration script to correct it. The edited script will not get run again on those environments.

    Currently there are only two work arounds we are aware of. Create a second migration script and leave the original incorrect one, both to be run in production. Or, manually go in to the [RedGateLocal].[DeploymentMetadata] and delete the rows that mark the script deployed.

    We would like to see a checkbox or similar feature to mark an edited migration script to be run again, even though the original version had already been run on some environments.

    Currently there is an option to edit migration scripts however edits will not get applied to other environments if the old version of the script was already run.

    Imagine the scenario where a migration script is created to update one record in a table that does not have it's data versioned. The script is checked in and deployed to the CI environment and the QA (test) environment. QA test finds that the update was incorrect. Development edits the migration script to correct it. The edited script will not get run again on those environments.

    Currently there are only two work… 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…)
    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. Remove operations prior to a CREATE statement when linking to .sqlproj files

    I'm linking to an existing database using a local folder. The database is linked in shared mode.

    The local folder was built by SSDT and contains a .sqlproj file. I'm notified of the beta functionality when linking, so I know SQL Source Control identifies the project as linking to SSDT.

    When I add a stored procedure, the resulting script starts with:
    SET QUOTEDIDENTIFIER ON
    GO
    SET ANSINULLS ON
    GO

    These statements don't compile in SSDT. The first statement in each script must be a create statement.

    I had removed these lines from the statement that I ran against SQL Server to create the procedure initially. After performing a commit, those statements are added in the resulting .sql script file.

    I checked the stored procedure using OBJECTDEFINITION(objectid) and find that those SET statements are not in the definition on the server. This indicates that SQL Source Control is adding those lines to the script.

    Please enable a way to prevent adding those lines. SSDT raises SQL70001 errors "The statement is not recognized in this context" as a result of those statements.

    Sorry if this is a duplicate request.

    I'm linking to an existing database using a local folder. The database is linked in shared mode.

    The local folder was built by SSDT and contains a .sqlproj file. I'm notified of the beta functionality when linking, so I know SQL Source Control identifies the project as linking to SSDT.

    When I add a stored procedure, the resulting script starts with:
    SET QUOTEDIDENTIFIER ON
    GO
    SET ANSINULLS ON
    GO

    These statements don't compile in SSDT. The first statement in each script must be a create statement.

    I had removed these lines from the statement that I ran against… 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…)
    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

19. Feature which should enforce user to lock the object before editing when administrator enables the restrictive policy for the users

    Feature which should enforce user to lock the object before editing when administrator enables the restrictive policy for the users

    If it is there it will be very much helpful for most of the development projects not testing and production.

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

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