588 results found

1. History window shouldn't prevent access to main window

   While viewing the history log you can't go to the main SSMS window. This is an issue if you want to look at source code history side by side with another window.

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

2. SourceControl - Ignore Replication Changes

   We use SourceControl in an MSSQL Merge Replicated database. The database uses ID pools, which generate contrains all the time with new pools for each table.

   The result is that all those tables show very frequently as if they were "changed", while that's technically true we don't care about those changes (those are system generated constrains, we don't want to source control that). It is basically garbage in our "changes" view, and it is actually preventing us from keeping our changes properly committed (hard to look for the changes one is doing, if there are 100 tables changes sitting around).

   Ideally there would be an option tell the system to ignore "replication generated objects" (maybe multiple options, one per each type of object that replication generates).

   Thanks.

   We use SourceControl in an MSSQL Merge Replicated database. The database uses ID pools, which generate contrains all the time with new pools for each table.

   The result is that all those tables show very frequently as if they were "changed", while that's technically true we don't care about those changes (those are system generated constrains, we don't want to source control that). It is basically garbage in our "changes" view, and it is actually preventing us from keeping our changes properly committed (hard to look for the changes one is doing, if there are 100 tables changes sitting around).

   … more

   53 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. distinguish between unique and non-unique indexes

   (This is actually relevant to both SQL Compare and SQL Source Control.)

   We really need to be able to distinguish between unique and non-unique indexes when comparing, checking in, and deploying database schema changes. ("Unique indexes" include primary keys, unique constraints, and unique indexes on tables and unique indexes on views; "non-unique indexes" include non-unique indexes on tables and views.)

   Unique indexes are essential to the database development process. They make a significant functional difference to the behavior of the database: they enforce business rules and referential integrity; they limit the data that can be entered into the database; foreign keys depend on them. Developers should be responsible for creating and maintaining all of the unique indexes on the development database, and an automated deployment process that uses SQL Compare and SQL Source Control should be able to deploy all database schema changes, including unique indexes, from the development database to the production database.

   On the other hand, non-unique indexes do not affect the database's behavior; they only affect the database's performance. Developers should not be responsible for maintaining non-unique indexes; they can't. A development database usually has a relatively small amount of test data in it, and a production database usually has a much larger amount of real data. SQL Server uses different indexes and different query execution plans depending on the amount and quality of data in the database, and the servers recommend different indexes depending on which queries get used the most frequently. A developer, running queries on the development database and looking at the execution plans to determine which indexes are needed, will get results that are not valid for the production database. In our case, it is also common for one set of queries to be heavily used one month and an entirely different set of queries to be heavily used the next month, so the developers would never be able to keep up with the production server's changing needs.

   Instead, we have a SQL Agent job that runs periodically on the production server to maintain non-unique indexes. The job reads and analyzes the system view sys.dmdbindexusagestats to determine which indexes are the least-recently used and the most-frequently updated, and drops them. It also reads and analyzes the system views sys.dmdbmissingindexgroupstats, sys.dmdbmissingindexgroups, and sys.dmdbmissingindex_details to determine which missing indexes are the most needed, and creates them. This index maintenance job frees up developers to do actual development instead of tracking down performance problems and fixing them.

   The problem is that SQL Compare and SQL Source Control do not distinguish between unique indexes and non-unique indexes; it will compare and synchronize either all of them or none of them. If we ignore indexes, then we can't deploy primary keys, unique constraints, unique indexes, or foreign keys (since foreign keys depend on unique indexes); if we include indexes, then the non-unique indexes created on the production server will be dropped in favor of the non-unique indexes that happen to exist on the development server, undoing all of the performance improvements made by the automatic index maintenance job.

   We would like the "Ignore indexes" option of SQL Compare and SQL Source Control to be split into two options, "Ignore unique indexes" and "Ignore non-unique indexes".

   (This is actually relevant to both SQL Compare and SQL Source Control.)

   We really need to be able to distinguish between unique and non-unique indexes when comparing, checking in, and deploying database schema changes. ("Unique indexes" include primary keys, unique constraints, and unique indexes on tables and unique indexes on views; "non-unique indexes" include non-unique indexes on tables and views.)

   Unique indexes are essential to the database development process. They make a significant functional difference to the behavior of the database: they enforce business rules and referential integrity; they limit the data that can be entered into the database; foreign… more

   8 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

4. Support for SourceGear Veracity
   8 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. Multiple comments per commit

   We are using a web hosted repository that is very slow. It would be good if we could make comments for multiple items being committed. i.e. proc 1 with comment 1, proc 2 with comment 2 etc.

   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…)
   3 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. I would like to be able to print to file (pdf, excel) the table of changes shown in source control.

   Print the changes displayed by source control to pdf, excel, csv.

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

7. Link source control to Schema, not database

   We couple applications with schemas, not databases. It would be great to link source control to just one schema, rather than the entire database. This way, we can source the code for the application and the database in the same branch

   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…)
   3 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. Bug: Highlighting changed objects - then they disappear

   BUG: When a table is changed it is moved from its alphabetic position in teh list to the bottom of the list and highlighted, which is a pain in large databases
   If you don't immediately commit the table and make more changes it is removed from the table list altogether and you have to refresh to get the table back again - I know this is the default behaviour for new tables but the highight, put in wrong place, remove action is wrong - it should either highlight and leave in place or wait until a refresh is done and then highlight in place

   BUG: When a table is changed it is moved from its alphabetic position in teh list to the bottom of the list and highlighted, which is a pain in large databases
   If you don't immediately commit the table and make more changes it is removed from the table list altogether and you have to refresh to get the table back again - I know this is the default behaviour for new tables but the highight, put in wrong place, remove action is wrong - it should either highlight and leave in place or wait until a refresh is done and… 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  ·  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. installed toolbelt this morning, uninstalled this evening due to SSMS UI impact...

   I am completely put off by Redgate taking over so much SSMS UI. I was very attracted to some of the tools, but can't work like this. Tried to find way to disable/hide them, but appears uninstall is only way.

   I want minimal UI intrusion until such time as I decide I like/want more UI intrusion. We need a way to dial it back to point where all redgate stuff optionally sits under single top menu and/or context menu.

   I reckon in meantime I will install tools in a throwaway VM so I can see how they work without impeding my day to day work.

   I am completely put off by Redgate taking over so much SSMS UI. I was very attracted to some of the tools, but can't work like this. Tried to find way to disable/hide them, but appears uninstall is only way.

   I want minimal UI intrusion until such time as I decide I like/want more UI intrusion. We need a way to dial it back to point where all redgate stuff optionally sits under single top menu and/or context menu.

   I reckon in meantime I will install tools in a throwaway VM so I can see how they work without impeding… more

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

10. Do Not Allow HG Commit without a FogBugz BugID/CaseID

    Currently with Tortoise Hg we can prevent a commit if the commit message does not contain a FogBugz bug/case ID. Based on a conversation with Red Gate support, SQL Source Control commit does not currently support this functionality. Please add it ASAP.

    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  ·  Support Additional Source Control Systems  ·  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. It says No database selected - select a database in object explorer. I do have a database selected in object explorer. How do I get started?
    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…)
    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

12. Spell Check on comments.

    Spell check on the comment text box would be helpful. Once a comment is checked into mercurial it is hard to fix the misspelled comments.

    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…)
    1 comment  ·  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

13. Add preemptive error checking

    Add preemptive error checking.
    One of our challenges is that it is too easy to break the get latest functionality. If a developer renames a column but doesn't rename all references (because he forgot to use Smart Rename) he is essentially breaking the database build. If I use Continues Integration to build the latest SQL changes, I have no bullet-proof way of ensuring that my database compiles at all time. I would like to ask Redgate to not allow a check-in which will break the build. I imagine that all that needs to be done is to ensure that first generation dependencies don't have errors. It would be nice if this is an option that can be turn on or off.

    Add preemptive error checking.
    One of our challenges is that it is too easy to break the get latest functionality. If a developer renames a column but doesn't rename all references (because he forgot to use Smart Rename) he is essentially breaking the database build. If I use Continues Integration to build the latest SQL changes, I have no bullet-proof way of ensuring that my database compiles at all time. I would like to ask Redgate to not allow a check-in which will break the build. I imagine that all that needs to be done is to ensure that first… more

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

14. Migrations Support for PlasticSCM

    I'd like to see migration scripts support for PlasticSCM. Why isn't something that is written as a "plugin"? Plastic isn't supported out of the box, but it's a simple enough matter to make a config file for it. Why can't the same be done for migrations? Allow the end user to create a config file (perhaps requiring the use of regular expressions for history parsing) or some other such mechanism. It seems like this should be a relatively straightforward thing to be able to do (it would also allow the customers to create the support for any SCM system they use).

    I'd like to see migration scripts support for PlasticSCM. Why isn't something that is written as a "plugin"? Plastic isn't supported out of the box, but it's a simple enough matter to make a config file for it. Why can't the same be done for migrations? Allow the end user to create a config file (perhaps requiring the use of regular expressions for history parsing) or some other such mechanism. It seems like this should be a relatively straightforward thing to be able to do (it would also allow the customers to create the support for any SCM system they… more

    9 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
    started  ·  Elizabeth Ayer responded

    Hello! We believe that this now works if you’re connecting to PlasticSCM with the working folder option in SQL Source Control. Before we close this request, though, we’re hoping that one of you with a real installation can check it out and let us know.

    If you don’t have the tool installed, you can download it from http://www.red-gate.com/products/sql-development/sql-source-control/.

    If you already have SQL Source Control you can get the new version via Check for updates in the Help menu of SQL Source Control inside SSMS.

    Thank you for sticking with us while we worked on this, and please keep the feedback coming!

15. Do changes have to be applied in order?

    SQL Source Control increments a Revision number after each change. Does this imply that I am required to apply all changes up to a given Revision in a second database? I really want to apply only selected changes, and in my own order.

    RELATED: If I select Revision 10 to apply to my database, and then select Revision 7, have I effectively removed changes for Revision 8, 9 and 10?

    Note that I am most concerned about DATA in these cases. The schema for this particular project is mostly stable. I'm just trying to keep track of data rows that determine program functionality (data-driven application).

    SQL Source Control increments a Revision number after each change. Does this imply that I am required to apply all changes up to a given Revision in a second database? I really want to apply only selected changes, and in my own order.

    RELATED: If I select Revision 10 to apply to my database, and then select Revision 7, have I effectively removed changes for Revision 8, 9 and 10?

    Note that I am most concerned about DATA in these cases. The schema for this particular project is mostly stable. I'm just trying to keep track of data rows that… 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…)
    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

16. Add comment attribute to SSMS display

    Add "Author" and "Comment" attributes (from History window) to Get Latest display on SSMS. The Owner column is not very useful.

    I would like to be able to select defect fixes or specific enhancements to apply to a version of a database. For example, changes can be made by a developer in a DEV environment and checked into Source Control. Then the DBA can apply select changes to the TEST environment database for more testing. Select changes can then move forward to an INTEGRATION testing environment for a deployment test before moving to PRODUCTION.

    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…)
    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. Search migration scripts for keywords

    It would be nice to do a quick search across all migration scripts for certain keywords. I.E. I'd like to look for all migration where I granted permissions. Or where I inserted rows into a specific table.

    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…)
    1 comment  ·  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

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

    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. Synchronize Replicated Database Environments // or Possible Workaround such as Filter of Table Columns, contraints, indexes, etc...

    Create a way I can synchronize:

    1. NON REPLICATED database X REPLICATED database
    2. REPLICATED database X REPLICATED Database

    Ability to syncronize tables/columns, views, sps, triggers, functions, indexes and constraints.
    Avoid displaying individual constraints used for replication. E.g. Constraints that use range of IDs, Indexes of merging, etc.

    == OR ==

    Allow me to:

    1. Filter Table COLUMNS by Name or part of it; E.g. 'rowguid', '% column name %'
    2. Filter Constraint Name or part of it; E.g. 'replidentity%'
    3. Filter Index by Name or part of it; E.g. 'MSmerge_%'
    61 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

20. Move Column Order

    the ability to move column order
    Example I would like the Owner Column next to the Object Name

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