Comments
Sort by recent activity
chrisqtran said:
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.
Hi! I'm getting an error when starting SSMS 20 with SQL Prompt 10.14.11.7894: [image] Transcript: SQL Prompt - error With TextMgrP.dll registration SQL Prompt has been disabled due to an error With the registration of a required DLL (TextMgrP.dll). To resolve the error, repair SQL Server Management Studio or Visual Studio from the Windows Control Panel.
I followed the instructions and repaired both SSMS and VS but it did not fox the issue. I submitted an error report to redgate via the built in tool. / comments
chrisqtran said:
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...
NathWilson said:
We released a fix for this today in SQL Prompt v10.6.16.
Thanks for the fix, works for me too! 🙂 / comments
NathWilson said:
We released a fix for this today in SQL Prompt v10.6.16.
Thanks for the fix, works for me too! 🙂
Same SQL Prompt version, same SSMS version. For me, the error does not occur immediately upon typing "@" though, but after selecting a table variable from the SQL prompt suggestions box. E.g.
Type "INSERT INTO @"
Select @tvp from the suggestions
Crash
/ comments
Same SQL Prompt version, same SSMS version. For me, the error does not occur immediately upon typing "@" though, but after selecting a table variable from the SQL prompt suggestions box. E.g.
Type...
FYI, they fixed this in version 9.5.20.11737. https://documentation.red-gate.com/sp9/release-notes-and-other-versions/sql-prompt-9-5-release-notes#SQLPrompt9.5releasenotes-9.5.20.11737 Thanks Redgate! [image] / comments
FYI, they fixed this in version 9.5.20.11737.https://documentation.red-gate.com/sp9/release-notes-and-other-versions/sql-prompt-9-5-release-notes#SQLPrompt9.5releasenotes-9.5.20.11737Thanks Redgate!
Jessica R said:
@SupiluliumaII, if you have a supported license please feel free to open a ticket as well b y emailing support@red-gate.com. Otherwise, I'll update here once we know more.
@Jessica R, thanks for the suggestion, I will do that. / comments
Jessica R said:
@SupiluliumaII, if you have a supported license please feel free to open a ticket as well b y emailing support@red-gate.com. Otherwise, I'll update here once we know more.
@Je...
Jessica R said:
Sorry to hear you're both still running into this! To help us narrow down where things are going wrong, can I just confirm: - Does this fail for every synonym? - Does it fail in every query, even a simple one that calls on the synonym?
bmrazik said:
yes, all synonyms no matter the query...you'll see above as well, that i lose peeking at index definitions on indexed views
Same here. I see no synonyms at all in suggestions, even in very simple queries. Peeking at synonyms' definitions does not work either. / comments
Jessica R said:
Sorry to hear you're both still running into this!To help us narrow down where things are going wrong, can I just confirm:- Does this fail for every synonym?- Does it fail in ...
It's been almost half a year - is there any progress on this issue? / comments
It's been almost half a year - is there any progress on this issue?
Hi Aaron,
yeah, that's what I thought [image]
Thanks for clarifying though.
BTW, this was your chance to come up with some awesome name like "Super Selection Function" or something... Missed that! :mrgreen: / comments
Hi Aaron,
yeah, that's what I thought
Thanks for clarifying though.
BTW, this was your chance to come up with some awesome name like "Super Selection Function" or something... Missed that! :mrgreen:
deathtospam wrote:
I also experience common crashes, albeit due to "Out of Memory" exceptions. At no point before I installed Red Gate did I ever get such errors. I'm running the SSMS tools against a server (not doing the work locally); my local machine has 8GB and utilization is never close to maxed when I get these errors.
In many cases, SQL Search is the only thing that I'm "running" in SSMS when the exception occurs -- it's not like it only happens when I run a world-ending query.
I think this could be the same issue that I experience (https://forums.red-gate.com/viewtopic.php?f=175&t=20747#p137922) when SQL Search defaults to "all databases" and starts indexing them. / comments
deathtospam wrote:
I also experience common crashes, albeit due to "Out of Memory" exceptions. At no point before I installed Red Gate did I ever get such errors. I'm running the SSMS tools ag...
csuire wrote:
SQLSearch2 sometimes detects the current database.
Othertimes it defaults to all databases.
For servers with LOTS of database, it can be annoying when it defaults to all databases.
The UI does not allow you to type a specific database name into the dropdown to aid in finding a specific database, which results in lots of scrolling.
When the SQL Search 2 database control has focus. Can you add support for typing the name of the database and have it narrow down the list as you type, and without using the mouse, select a specific database from the list.
Maybe also add an option to prevent SQL Search 2 from defaulting to All Databases. When the option it turned on, it would default to no database -- or be better at detecting the current database.
I agree with the OP that the behaviour of SQL Search to sometimes default to "all databases" is an issue.
I could live with the extra scrolling and having to deselect and select databases, but the real problem is that when all databases are selected, SQL Search starts to index all those databases. On a server with 300+ databases that takes a lot of RAM on the client and eventually leads to SQL Search crashing and me having to restart SSMS.
Could you please fix this? I think SQL Search should either never default to "all databases" or have an option to disable automatic indexing of selected databases.
Thanks. / comments
csuire wrote:
SQLSearch2 sometimes detects the current database.
Othertimes it defaults to all databases.
For servers with LOTS of database, it can be annoying when it defaults to all databases....