Best Of
Re: SQL Compare 15.3.11.27029 Error: Input string was not in a correct format
Found an easy solution, locate SQLPrompt.Format.CommandLine.exe on your computer (was in "D:\Program Files (x86)\Red Gate\SQL Prompt 9" on my computer).
using Visual Studio (File-->Open on the EXE) correct the Product Version from 10.14.22.11347+e4f26ea... to 10.14.22.11347). The issue is the Product Version for the file isn't valid for using with System.Version(string) method.
Hope this helps someone else who likes to be able to use SQL Prompt and SQL Compare
using Visual Studio (File-->Open on the EXE) correct the Product Version from 10.14.22.11347+e4f26ea... to 10.14.22.11347). The issue is the Product Version for the file isn't valid for using with System.Version(string) method.
Hope this helps someone else who likes to be able to use SQL Prompt and SQL Compare
cstrub
12 ·
Re: SQL Prompt for SSMS Pre-Release 20
Hi all,
I am happy to share that SQL Prompt is now available for SSMS 20. I've listed the installer for you to use:
https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_10.14.11.7894.exe
Let me know how it works for you.
chrisqtran
6 ·
Problem after update to Visual Studio 17.8
Hi.
We've just updated Visual Studio to the latest version, 17.8. Since then, the plugin crashes on build/cleanup or even opening the SCA tool window.
The error ->
MSBUILD: Error: : Method not found: 'Boolean Microsoft.Data.SqlClient.SqlConnectionStringBuilder.get_Encrypt()'.: Method not found: 'Boolean Microsoft.Data.SqlClient.SqlConnectionStringBuilder.get_Encrypt()'.
VS Version : 17.8
SCA extension version : 4.6.23312.2442
Thanks
We've just updated Visual Studio to the latest version, 17.8. Since then, the plugin crashes on build/cleanup or even opening the SCA tool window.
The error ->
MSBUILD: Error: : Method not found: 'Boolean Microsoft.Data.SqlClient.SqlConnectionStringBuilder.get_Encrypt()'.: Method not found: 'Boolean Microsoft.Data.SqlClient.SqlConnectionStringBuilder.get_Encrypt()'.
VS Version : 17.8
SCA extension version : 4.6.23312.2442
Thanks
JeromeL
5 ·
Re: SQL Prompt Error with TextMgrP.dll Registration
Ran into this as well after fresh install on a new laptop with the newest version of SSMS as of 3/22/2023 and visual studio 2022. I searched my computer and found the dll in C:\Program Files (x86)\Microsoft SQL Server Management Studio 19\Common7\IDE\Automation
Run command line as administrator and run;
regsvr32 "C:\Program Files (x86)\Microsoft SQL Server Management Studio 19\Common7\IDE\Automation\TextMgrP.dll"
Good to go for me!
Run command line as administrator and run;
regsvr32 "C:\Program Files (x86)\Microsoft SQL Server Management Studio 19\Common7\IDE\Automation\TextMgrP.dll"
Good to go for me!
Dinomite
5 ·
Is there a way to restore and use the old Tab History rather than the new SQL history?
The new SQL history window is useless to me, i see no efficient way of searching and sorting the results, and the fact that it takes over the entire window is horrible. These are my opinions of course but I use SQL tool belt and SQL Prompt a lot and this has seriously impacted my production.
DanMelson
5 ·
Re: Is there a way to restore and use the old Tab History rather than the new SQL history?
I'll add some thoughts to this one. The sorting is horrible, once you search there appears to be no logic as to what will show up in the listing; even when using advanced search. A default sort of date would be wonderful, or better yet give us options in the Advanced Search for Sort By where we can pick a default or change to what we want to see.
On the main page before searching grouping based on naming is useless because not everyone is saving every query with a logical name so we are accustomed to having SQLQuery##.sql as a name, so on any given day I may have 50 different queries that i've opened up and closed that all have SQLQuery1.sql as the "name" but they have nothing to do with each other so the History Grouping is a mis-mash of 50 different things and doesn't help us find anything. I've seen a lot of maybe you should use this or that, but I've dug through the limited documentation available and it's not helpful and not even you guys have updated quick reference to include the new History stuff https://assets.red-gate.com/products/sql-development/sql-prompt/assets/sql-prompt-quick-reference.pdf
On the main page before searching grouping based on naming is useless because not everyone is saving every query with a logical name so we are accustomed to having SQLQuery##.sql as a name, so on any given day I may have 50 different queries that i've opened up and closed that all have SQLQuery1.sql as the "name" but they have nothing to do with each other so the History Grouping is a mis-mash of 50 different things and doesn't help us find anything. I've seen a lot of maybe you should use this or that, but I've dug through the limited documentation available and it's not helpful and not even you guys have updated quick reference to include the new History stuff https://assets.red-gate.com/products/sql-development/sql-prompt/assets/sql-prompt-quick-reference.pdf
alegend2u
6 ·
Re: Is there a way to restore and use the old Tab History rather than the new SQL history?
@alegend2u I am 100% on the same page, the new SQL History is simply broken.
I wrote a cursor query a few weeks ago and then used it for several days while I was troubleshooting and testing an issue. Now when I enter the keyword CURSOR into SQL History's search, it doesn't return any results at all. If I try to use a partial match with wildcards like *cur* it brings up completely unrelated queries that DO NOT have a match on *cur* for some reason. One query it brought up as a match for *cur* had highlighted "SELECT DISTINCT" as the matching section of the result, which doesn't even have all the letters, let alone in the right order.
I used to rely on Tab History heavily, and now its replacement is completely useless and I don't see how it could have been released in such a state.
I wrote a cursor query a few weeks ago and then used it for several days while I was troubleshooting and testing an issue. Now when I enter the keyword CURSOR into SQL History's search, it doesn't return any results at all. If I try to use a partial match with wildcards like *cur* it brings up completely unrelated queries that DO NOT have a match on *cur* for some reason. One query it brought up as a match for *cur* had highlighted "SELECT DISTINCT" as the matching section of the result, which doesn't even have all the letters, let alone in the right order.
I used to rely on Tab History heavily, and now its replacement is completely useless and I don't see how it could have been released in such a state.
dougcpremier
7 ·
Re: How to downgrade to the latest version, containing "Tab history"?
David - Thank you for letting us now how to do this. That said I want to give Red-Gate (not you specifically) a piece of mind about this. I'm all for advancing/upgrading your products & services to continually try to improve them. The issue here is that Red-gate took it upon themselves to replace a highly useful and VERY easy to user feature in the software we pay annually to use with something that is far from easy or useful and which works like as if it was made by someone with little to no experience with what the products user want. I imagine SQL History was teh result of user request but when it was rolled out it should have been a separate feature allowing the paying customer to choose it or to stay with the Tab History. Until this I have never been more than mildly bothered by something Red-gate did to one of its products. I hope those at Red-Gate who are teh decision makers are listening to how users are unhappy with how this was pushed out.dkim1999 said:Hi there,Thank you for reaching out and I apologize that you are running into issues with SQL Prompt.You can revert back to Tab History by downgrading to the following version:Kind Regards,David K.Product Support Engineer
EdCarden
5 ·
Tab History Removal - Why??????
With the removal of Tab History from SQL Prompt I'm sure I'm not the only one tearing my hair out in frustration in using what is supposed to replace it. i.e. The awful SQL History
Yet another example of Redgate not listening to the paying customer who use SQL Prompt day in, day out.
I was using Tab History on a daily basis. It was perfect for my needs and didn't have any problems.
Now, for reasons I cannot fathom it has just been removed and we're told to use a replacement that is a poor substitute.
Does anybody else feel like I do? If so, then add your comments. I'm sure there is room for both Tab History and SQL History in SQL Prompt. So please Redgate bring back Tab History!
Yet another example of Redgate not listening to the paying customer who use SQL Prompt day in, day out.
I was using Tab History on a daily basis. It was perfect for my needs and didn't have any problems.
Now, for reasons I cannot fathom it has just been removed and we're told to use a replacement that is a poor substitute.
Does anybody else feel like I do? If so, then add your comments. I'm sure there is room for both Tab History and SQL History in SQL Prompt. So please Redgate bring back Tab History!
jimVisage1980
6 ·
Re: SQL Prompt Error '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
Hi all, i had same problem after i accidentally hit the power switch.
To fix the issue without re-installing SQL Prompt what I did was
1) Exit SQL Management studio
2) Go to folder C:\Users\myuser\AppData\Local\Red Gate\SQL Prompt 10\
3) Rename the file (to test it first) RedGate_SQLPrompt_CommonUI_Options_UIOptions.xml to something else like RedGate_SQLPrompt_CommonUI_Options_UIOptions_old.xml
4) Run SQL Management studio
This will then re-generate this file. It seems this file got corrupted (i.e. its empty) once i run it up and worked I removed renamed file
To fix the issue without re-installing SQL Prompt what I did was
1) Exit SQL Management studio
2) Go to folder C:\Users\myuser\AppData\Local\Red Gate\SQL Prompt 10\
3) Rename the file (to test it first) RedGate_SQLPrompt_CommonUI_Options_UIOptions.xml to something else like RedGate_SQLPrompt_CommonUI_Options_UIOptions_old.xml
4) Run SQL Management studio
This will then re-generate this file. It seems this file got corrupted (i.e. its empty) once i run it up and worked I removed renamed file
Steve_Paxton
6 ·
