6 results found

1. Find results highlighted on scrollbar

   In SSMS, when you search for a term, all locations of that term are highlighted on the scrollbar, making it easy to navigate to the locations of that term and to know where they appear in the file. In dbForge Studio, you can bookmark all, but that requires you to scroll through the entire document to find all instances and does not provide a complete picture of all of the places the term appears.

   This is a very important feature that is missing for me as I rely on that heavily in SSMS. I would like to see similar functionality implemented in dbForge Studio.

   In SSMS, when you search for a term, all locations of that term are highlighted on the scrollbar, making it easy to navigate to the locations of that term and to know where they appear in the file. In dbForge Studio, you can bookmark all, but that requires you to scroll through the entire document to find all instances and does not provide a complete picture of all of the places the term appears.

   This is a very important feature that is missing for me as I rely on that heavily in SSMS. I would like to see similar functionality… 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…)
   planned  ·  1 comment  ·  Features  ·  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. On the customer License Information page, add a user editable field where we can log who has which license.

   I purchase the licenses for my dev team, so when I purchase two licenses, one for myself (SQL Tools) and a separate on for one of my devs (Schema Compare) I would like to indicate which is assigned to whom. Currently on the License information page, both appear assigned to me. While two folks is easy, if we grow our usage of your products further, I would like to know who I've assigned which licenses to, while keeping them all under the one account.

   All I'm looking for is a field that I as the customer can note this type of information in. The field would be part of the LicenseID row, and unique to the LicenseID (one per License ID).

   This will allow an option for organizations like ours who prefer to keep licensing of this type consolidated to be able to document on the license which developer is assigned which LicenseID.

   I purchase the licenses for my dev team, so when I purchase two licenses, one for myself (SQL Tools) and a separate on for one of my devs (Schema Compare) I would like to indicate which is assigned to whom. Currently on the License information page, both appear assigned to me. While two folks is easy, if we grow our usage of your products further, I would like to know who I've assigned which licenses to, while keeping them all under the one account.

   All I'm looking for is a field that I as the customer can note this type… 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…)
   planned  ·  0 comments  ·  Features  ·  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. history

   Please move the Clear button for Query History from the main UI screen to be in the Options menu. In context, it seems like it is going to clear the search filters rather than wiping out the entire query history. It does warn you - but the history is so useful and important. Clearing it out should be a harder, more explicit step than just clicking twice. Not that I've done that... Multiple 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…)
   planned  ·  2 comments  ·  Features  ·  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. pin tab

   how is possible there is no simple thing as pin tabs?

   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…)
   planned  ·  1 comment  ·  Features  ·  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. remote changes source control

   For source control (GIT) at the remote changes tab add a ignore/delete option.

   I started working with the database and deleted/renamed some stored procedures. When I detached and attached my source control (GIT) it wants to add the procedures which I have removed.
   This is fine when someone else changed it, but now I specifically want to delete this procedures. When working with this I can add them again, to delete them afterwards, or I can delete them in the folder and check them in with GIT, bypassing dbForge.

   The easy solution would be to add a ignore/delete/keep local option which would ignore the 'Remote changes' and save my database version to GIT.

   For source control (GIT) at the remote changes tab add a ignore/delete option.

   I started working with the database and deleted/renamed some stored procedures. When I detached and attached my source control (GIT) it wants to add the procedures which I have removed.
   This is fine when someone else changed it, but now I specifically want to delete this procedures. When working with this I can add them again, to delete them afterwards, or I can delete them in the folder and check them in with GIT, bypassing dbForge.

   The easy solution would be to add a ignore/delete/keep local option… 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…)
   planned  ·  1 comment  ·  Features  ·  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. Detach stored SQL query from SQL connection

   At present, if I developed a SQL query, stored it and try to load it back into dbForge at a later date, dbForge 'remembers' the SQL connection it is associated with and tries to connect automatically. I want to be able to disable this behaviour via options - eg opening file does NOT try to be clever.

   EXTENDED RATIONALE

   In common usage, the feature is quite useful. Unfortunately, in some of the projects I am working with, I have to constantly switch between different environments (prod, pre-prod, demo, devops, etc) protected by external VPN. All environments are hosting the same databases, but, due to security, I could only be connected to one environment (and hence one particular database) at a time.

   It is common for me to use the same stored SQL (after all, all environments contains essentially the same schema). But right now, if I open SQL script which was previously executed in a different environment, dbForge freezes while it tries to connect (which it cannot), which is annoying and time wasting.

   To be clear - I do NOT want to get rid of existing functionality - it remains highly useful in some projects. But I want to be able to control it via Options or Settings, to be able to switch it on and off, as needed.

   At present, if I developed a SQL query, stored it and try to load it back into dbForge at a later date, dbForge 'remembers' the SQL connection it is associated with and tries to connect automatically. I want to be able to disable this behaviour via options - eg opening file does NOT try to be clever.

   EXTENDED RATIONALE

   In common usage, the feature is quite useful. Unfortunately, in some of the projects I am working with, I have to constantly switch between different environments (prod, pre-prod, demo, devops, etc) protected by external VPN. All environments are hosting the same… 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…)
   planned  ·  2 comments  ·  Features  ·  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