30 results found

1. SQL Test Allow for Custom tSQLt builds

   Currently SQL Test installs the 1.0.5873.27393 version of tSQLt. However there are more current builds available. Instead of packaging tSQLt as a DLL in the project, could you instead allow users to provide a customization that allows users to provide a path to tSQLt zip file or to specify DACPAC file (which is now provided in the latest release of tSQLt)?

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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

   Submit Rating

2. SQL Doc quality of life improvements

   SQL Doc is useful but painful to use at the same time. Some things I think would make it a better product are as follows:

   1) Darkmode, there is so much white on the screen, it hurts, literally.
   2) The ability to save all the changes with a single button. Why do we have to commit every single update one at a time? Can we not manage state in the app?
   3) As stated in other suggestions, the ability to customize the attribute would be great.
   4) Can we get an option to change the font/font size used in the application? Those of us running large screens would appreciate it.
   5) would it be possible to set a template for the property entry, for example, I want all the entered data to follow a set pattern of information. As it is, even with the best intentions, it's too easy to drift in style causing reediting.

   SQL Doc is useful but painful to use at the same time. Some things I think would make it a better product are as follows:

   1) Darkmode, there is so much white on the screen, it hurts, literally.
   2) The ability to save all the changes with a single button. Why do we have to commit every single update one at a time? Can we not manage state in the app?
   3) As stated in other suggestions, the ability to customize the attribute would be great.
   4) Can we get an option to change the font/font size used in the… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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

   Submit Rating

3. Use SQL Doc to document Azure Fabric SQL Warehouse.

   Use SQL Doc to document Azure Fabric SQL Warehouse.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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

   Submit Rating

4. Allow SQL Doc to use Markdown

   Allow documentation stored to follow Markdown standards to allow for bulleted lists, bold, and other stylizations that Markdown supports

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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

   Submit Rating

5. Provide database alias or friendly name option for documentation output

   This is for similar reasons as posted in this existing feature request:
   https://redgate.uservoice.com/forums/936348-sql-toolbelt-essentials/suggestions/44666800-sql-doc-cover-page-options

   We as vendors provide database documentation to our clients for our product. We would like a way to alias, or otherwise provide a friendly name, to the database we target when generating PDF documentation. It is not desired to expose internal databases name. We would rather see the database show up throughout the documentation with a friendly name like "Template Database." Rather than exposing an internal database naming scheme. This friendly name would be used in the cover page, table of contents, and anywhere it showed throughout the PDF documentation.

   It is not desirable to have to export generation to Microsoft Word, customize, then resave as PDF. For starters, this makes the process harder to fully automate as it involves human intervention. Secondly, PDFs generated from Microsoft Word have a lot of size bloat due to how Microsoft embeds styles and fonts into PDF. A 2.13MB MS Word file can turn into a 13.7MB PDF.

   This sort of feature would also be incredibly useful for the server information and documentation file path. This is sensitive information that should not be exposed to customers.

   This is for similar reasons as posted in this existing feature request:
   https://redgate.uservoice.com/forums/936348-sql-toolbelt-essentials/suggestions/44666800-sql-doc-cover-page-options

   We as vendors provide database documentation to our clients for our product. We would like a way to alias, or otherwise provide a friendly name, to the database we target when generating PDF documentation. It is not desired to expose internal databases name. We would rather see the database show up throughout the documentation with a friendly name like "Template Database." Rather than exposing an internal database naming scheme. This friendly name would be used in the cover page, table of contents, and anywhere it showed throughout… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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

   Submit Rating

6. Provide database alias / friendly name option for documentation output

   This is for similar reasons as posted in this existing feature request:
   https://redgate.uservoice.com/forums/936348-sql-toolbelt-essentials/suggestions/44666800-sql-doc-cover-page-options

   We as vendors provide database documentation to our clients for our product. We would like a way to alias, or otherwise provide a friendly name, to the database we target when generating PDF documentation. It is not desired to expose internal databases name. We would rather see the database show up throughout the documentation with a friendly name like "Template Database." Rather than exposing an internal database naming scheme. This friendly name would be used in the cover page, table of contents, and anywhere it showed throughout the PDF documentation.

   It is not desirable to have to export generation to Microsoft Word, customize, then resave as PDF. For starters, this makes the process harder to fully automate as it involves human intervention. Secondly, PDFs generated from Microsoft Word have a lot of size bloat due to how Microsoft embeds styles and fonts into PDF. A 2.13MB MS Word file can turn into a 13.7MB PDF.

   This sort of feature would also be incredibly useful for the server information and documentation file path. This is sensitive information that should not be exposed to customers.

   This is for similar reasons as posted in this existing feature request:
   https://redgate.uservoice.com/forums/936348-sql-toolbelt-essentials/suggestions/44666800-sql-doc-cover-page-options

   We as vendors provide database documentation to our clients for our product. We would like a way to alias, or otherwise provide a friendly name, to the database we target when generating PDF documentation. It is not desired to expose internal databases name. We would rather see the database show up throughout the documentation with a friendly name like "Template Database." Rather than exposing an internal database naming scheme. This friendly name would be used in the cover page, table of contents, and anywhere it showed throughout… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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

   Submit Rating

7. Multiscript Functionality Request

   Hello,
   Can the ability to add a search bar on the scripts to execute side. We have multiple scripts on that side waiting for approval and once approved we must find it by manually searching the script name. It hasn’t been an issue, but it would make life easier. Also is it possible to change size of font? There is a dat file in the location C:\Users<username>\AppData\Roaming\Red Gate\SQL Multi Script 1.Could it also be set to append the .dat file instead of overwrite so that multiple users can work of the same .dat file. If one person has it open using symlinks or mslink once it is closed and saved the if another person closes the application with having their window open prior to the 1st person changes the changes are overwritten every time the application is closed and saved. If there is no way to append can functionality be added setup multiuser capability for one tool across a network share.
   That would also be great.

   Hello,
   Can the ability to add a search bar on the scripts to execute side. We have multiple scripts on that side waiting for approval and once approved we must find it by manually searching the script name. It hasn’t been an issue, but it would make life easier. Also is it possible to change size of font? There is a dat file in the location C:\Users<username>\AppData\Roaming\Red Gate\SQL Multi Script 1.Could it also be set to append the .dat file instead of overwrite so that multiple users can work of the same .dat file. If one person has it open… more

   •  

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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

   Submit Rating

8. SQL Doc needs a better user-interface

   SQL Doc needs a better user-interface for navigating object between objects. For instance, providing History in order to navigate back and forth.

   In addition, the tree view in the left pane needs to support proper shortcut keys and access key. For instance, typing in the current tree view does not work. Arrow keys should expand or collapse nodes. Even clicking on a node result in slow response slow screen updates without any progress indicator.

   Lastly, there needs to be an object search feature. I should be able to search on "user" to list all objects, just like "SQL Search".

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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

   Submit Rating

9. Add option to stop Multi Script reopening the last saved project.

   SQL Multi Script automatically re-opens the previous saved project when opening the application. Even when a New Project is created, if it's not saved the app opens the last saved project when it next starts. I have to manually move/rename the old file or edit the <recentProjectPaths> element in the data file to prevent it occurring.

   Add an option to turn this off.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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

   Submit Rating

10. Usage

    For a table, in use section, add informations to show where the table has updates / inserts / deletes

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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

    Submit Rating

11. Some possible enhancements for SQL Test

    1) On the Code Coverage tab, it would be great if we could sort by any of these columns, rather than be stuck with having them in ‘coverage % descending’ order only

    2) Also on the code coverage tab, could we have a new column to show 'Uncovered Statement Count' please? For those who are being asked to get the code coverage percentage higher, this feature (combined with (1) above) would help identify the SPs that would give the biggest ‘bang for our buck’ if tests are created

    3) Our database has about 2000 stored procedures, so our test classes relate to functional areas rather that individual SPs, as we didn’t want thousands of classes/schemas. What we hadn’t considered was that when we change an SP and want to run the tests to verify functionality and coverage, we need to run the whole test class, which can take a while. It would be really nice if we could highlight a set of tests from the UI and just execute those that are highlighted.

    1) On the Code Coverage tab, it would be great if we could sort by any of these columns, rather than be stuck with having them in ‘coverage % descending’ order only

    2) Also on the code coverage tab, could we have a new column to show 'Uncovered Statement Count' please? For those who are being asked to get the code coverage percentage higher, this feature (combined with (1) above) would help identify the SPs that would give the biggest ‘bang for our buck’ if tests are created

    3) Our database has about 2000 stored procedures, so our test classes… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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

    Submit Rating

12. Include Indexes in SQL Search tool

    SQL Search is able to go through that list of programmable db objects, but why not include indexes as well? If as developers we want to find something in our db instance, there should be a tool to include everything we are looking to find. It is a "search" tool; has that in the name. The tool is not called "Programmable Objects SQL Search", so why limit the search?

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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

    Submit Rating

13. Add visibility for test functions

    When you test a function (ie use the tsqlt.FakeFunction method) you have to specify a function that will replace the function being faked. This creates a dependency on that function. Currently these faked functions aren't visible in SQL Test. It would be great to be able to see them listed in the UI so that developers can see them. The functions are typically created within the same schema/class as the the test(s) so that's where they should be displayed. The names of the functions won't typically start with test and won't have any extended properties on them as they are just normal functions, but are identifiable because they are in the test schema/class. It would be helpful to have some visible distinction that they aren't tests (maybe italicize the function name or give it a special icon instead of the normal bullet point?)

    When you test a function (ie use the tsqlt.FakeFunction method) you have to specify a function that will replace the function being faked. This creates a dependency on that function. Currently these faked functions aren't visible in SQL Test. It would be great to be able to see them listed in the UI so that developers can see them. The functions are typically created within the same schema/class as the the test(s) so that's where they should be displayed. The names of the functions won't typically start with test and won't have any extended properties on them as they are… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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

    Submit Rating

14. Support Test Setup in SQL Test

    The tSQLt framework allows for the existence of a test procedure named Setup within a test class that can be used to create data once instead in each of the individual tests. However, in SQL test if you create a test named Setup it makes the test name be test Setup which isn't what is needed. You can see the documentation of the Setup in the following documentation for tSQLt:
    https://tsqlt.org/130/creating-and-running-test-cases-in-tsqlt/
    Can you make it so that if the test name specified is Setup or setup (or any case variation thereof) that it will not prepend the word test to the new test name. When the test is created it should be displayed in the UI, but not executed when you run the test via the UI because the framework executes the procedure. This is because Setup is not a test, it is a component of all the tests in that class, so it should not be explicitly executed by SQL Test but needs to be visible in the UI so that developers know that it exists as part of the tests.

    The tSQLt framework allows for the existence of a test procedure named Setup within a test class that can be used to create data once instead in each of the individual tests. However, in SQL test if you create a test named Setup it makes the test name be test Setup which isn't what is needed. You can see the documentation of the Setup in the following documentation for tSQLt:
    https://tsqlt.org/130/creating-and-running-test-cases-in-tsqlt/
    Can you make it so that if the test name specified is Setup or setup (or any case variation thereof) that it will not prepend the word test to… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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

    Submit Rating

15. Make SQL Test Template File Location Configurable

    In SQL Test there is a file called TestCaseTemplate.sql that is in the Program Files folder for SQL Test.

    Can the folder location be configurable so that we can put the file in source control and then have it pointed at the folder where we have our local repos on our development machine?

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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

    Submit Rating

16. shelly.miller@rev.io

    Would like SQL Data Generator or automatically detect new or modified objects via the CLI and, if that option to automatically add new objects to the project has been chosen, add data to those new objects when the CLI is run.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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

    Submit Rating

17. Implement configurable caption property

    Stumbled upon this feature from dbForge:

    https://docs.devart.com/sqlcomplete/setting-up-sql-complete/ssms-caption-options.html (adding the section "SSMS Caption" to Options making it possible to customize the pattern for the main window title.

    I frequently use to instances of SSMS - one running under my standard account and one running with an elevated account. I would use a feature like SSMS Caption to make it easy to distinguish a window from the standard instance and a window from the elevated instance.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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

    Submit Rating

18. Diagramming tool

    If I'm designing a new application or adding a new feature to an existing one, I'll typically use the SQL Diagram feature in SSMS to design the tables and their relationships. It works okay, but has some limitations:

    1) It's tied to a single server. If I want to get those diagrams onto a new server, well, I don't know a way to do it so they typically only exist on our dev servers. It'd be great to have a tool that kept these outside of SSMS and the SQL server. It wouldn't update the database on save, but would instead batch up changes until I was ready to commit them to a server.

    2) It would be great if this combined some features of multi script and sql compare, and could be applied to a defined group of servers in one go, bringing all aspects of the affected schemas on those servers into line with the diagram

    3) Every time I start a new diagramming session I need to set up my own custom table format, with the fields I care about. SSMS doesn't remember this when I start another new diagram. The tool I'm envisaging would remember.

    4) Adding existing tables to the diagram from the SQL database (as in the SSMS tool), but with an option to treat these as part of the diagram or as external references (our model tables can have a relationship with them, but they remain read only in terms of the diagram)

    If I'm designing a new application or adding a new feature to an existing one, I'll typically use the SQL Diagram feature in SSMS to design the tables and their relationships. It works okay, but has some limitations:

    1) It's tied to a single server. If I want to get those diagrams onto a new server, well, I don't know a way to do it so they typically only exist on our dev servers. It'd be great to have a tool that kept these outside of SSMS and the SQL server. It wouldn't update the database on save, but would… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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

    Submit Rating

19. gMSA support for all RedGate products

    gMSA support for all RedGate products
    Increased security, less maintenance after initial setup. Compliance and auditors are constantly pushing for these changes.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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

    Submit Rating

20. Data Compare and Sql Compare - Option to Uninstall Old Major Version

    When upgrading and Data Compare or Sql Compare are going to a Major version, it would be nice to have an option to uninstall the old version. i.e. version 15 released and I didn't have an option to have it uninstall 14, so I had to manually uninstall it and make sure I didn't lose my settings / snippets / etc...

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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

    Submit Rating