Comments
Sort by recent activity
Hi there, Thank you for reaching out and I apologize that you are running into issues with SQL Prompt. I was able to recreate your issue when trying to search through tab history using Ctrl + Shift + X.
However, do you still face this issue when you open SQL History using the tab at the top and then searching? Thank you! David K. Product Support Engineer
/ comments
Hi there,Thank you for reaching out and I apologize that you are running into issues with SQL Prompt.I was able to recreate your issue when trying to search through tab history using Ctrl + Shift +...
Hi Henrik, Thank you for sharing the logs. It appears that this is a known issue by the development team and they are actively looking into a fix. I can update you once a fix is released. Kind Regards, David K. Product Support Engineer
/ comments
Hi Henrik,Thank you for sharing the logs.It appears that this is a known issue by the development team and they are actively looking into a fix.I can update you once a fix is released.Kind Regards,...
Hi Henrik, Thank you for reaching out and I apologize that you are running into issues with SQL Prompt. When SSMS crashes, is there an error message accompanied with it? In addition, are there any errors within the SQL Prompt log files? Thank you! David K. Product Support Engineer
/ comments
Hi Henrik,Thank you for reaching out and I apologize that you are running into issues with SQL Prompt.When SSMS crashes, is there an error message accompanied with it?In addition, are there any err...
Hi there, Thank you for reaching out and I apologize that you are running into issues with SQL Prompt. In the latest versions of SQL Prompt, the development team has added the Sqlhistory.DB file along with the SavedTabs.DB file. You should have both within your SQL Prompt 10 folder. Can you please try these troubleshooting steps: 1. Browse to %localappdata%\Red Gate\SQL Prompt 10\ 2. Delete the file "SqlHistory.db" (make a copy elsewhere first) 3. Relaunch SSMS You won't lose your Tab History (since it is stored in another file) and when you open a new session of SSMS, SQL Prompt creates a new SqlHistory.db file. Kind Regards, David K. Product Support Engineer / comments
Hi there,Thank you for reaching out and I apologize that you are running into issues with SQL Prompt.In the latest versions of SQL Prompt, the development team has added the Sqlhistory.DB file alon...
Hi Jonathan, I apologize for the delay in response. This seems to be a known issue by the developers and they are currently taking a look at it. I do not currently have a time-frame of when this issue will be fixed, but I can update this forum post once a fix is released. Kind Regards, David K. Product Support Engineer
/ comments
Hi Jonathan,I apologize for the delay in response.This seems to be a known issue by the developers and they are currently taking a look at it.I do not currently have a time-frame of when this issue...
Hi Jonathan, Thank you for the update. Is there an error message that pops up after it crashes or does it just crash. Kind Regards, David K. Product Support Engineer / comments
Hi Jonathan, Thank you for the update.Is there an error message that pops up after it crashes or does it just crash.Kind Regards,David K.Product Support Engineer
Hi MarcGervais, Thank you for reaching out about SQL Monitor. It would be useful if we could assign tags to individual databases. While it is currently not a feature of SQL Monitor, I highly recommend that you log it as a feature request in our UserVoice page for SQL Monitor(https://sqlmonitor.uservoice.com/forums/91743-suggestions). This way our development team will have visibility of it, and other customers will be able to vote for it. Thank you! David K. Product Support Engineer
/ comments
Hi MarcGervais,Thank you for reaching out about SQL Monitor.It would be useful if we could assign tags to individual databases. While it is currently not a feature of SQL Monitor, I highly recommen...
Hi there, I am glad to hear that it is working now. Have a great day! David K. Product Support Engineer
/ comments
Hi there,I am glad to hear that it is working now.Have a great day!David K.Product Support Engineer
Hi there, Thank you for reaching out and I apologize that you are running into issues with SQL Prompt. The most recent version of SQL Prompt(10.12.5) has some issues regarding viewing tab history.
There is currently a workaround but because you are migrating your tabs
from one machine to another, I am not too sure if it will still work. You
will need to close down SSMS then browse to %localappdata%\Red Gate\SQL
Prompt 10\ and delete only the file named "SqlHistory.db" and then
relaunch SSMS. You should now be able to view Tab History. This
file is the new format for saved tab history. So when opening the new
version of SQL Prompt for the first time, it should take the existing
"SavedTab.db" and convert it to the new format. Due to an issue with
this release the initial "SqlHistory.db" is corrupt so deleting it
should prompt SQL Prompt to re-create the file upon re-opening SSMS.
Let me know how it goes! David K. Product Support Engineer
/ comments
Hi there,Thank you for reaching out and I apologize that you are running into issues with SQL Prompt.The most recent version of SQL Prompt(10.12.5) has some issues regarding viewing tab history.
Th...
Hi there, Thank you for reaching out and I apologize that you are running into issues with SQL Prompt. Can I ask what version of Visual Studio and SQL Prompt you are running? Kind Regards, David Kim Product Support Engineer
/ comments
Hi there,Thank you for reaching out and I apologize that you are running into issues with SQL Prompt.Can I ask what version of Visual Studio and SQL Prompt you are running?Kind Regards,David KimPro...