16 results found
-
VSCode integration.
I've used SQL Prompt for 20 years. I would LOVE VSCode integration.
3 votes -
Sql prompt support for Dedicated SQL pool
Add support for Dedicated SQL pool on Azure Synapse.
2 votes -
Reprompt for authentication on MFA for Azure SQL Databases for expired tokens
When you use the interactive sign in with AD option with a SQL database, it's not very stable in it's connection. I suspect it's either not supporting the refresh tokens (if it has them) or hasn't got the right detection for an expired token.
When authentication fails in this mode, it gives up silently and functionality starts to turn off as it can't connect to the database - see attached log.
I have to close SSMS every 3 hours or so, which forces SQL prompt to re-authenticate and get a new token. Turning on/off suggestions does not trigger a reauthentication.
1 vote -
Add support for Fabric warehouses and lake houses
Add support basic intellisense support for Fabric warehouses and lake houses.
13 votes -
AI
AI suggestions.
I'm not part of your AI program waiting list. However here what I suggest.
Do not make the AI part of your program an only cloud-based solution. There are plenty of opensource code models free for commercial use that can be ran locally on a PC. These models can also run under CPU but will up the memory to enable this feature requirements for AI on client side only. It's too dangerous for Redgate to store this information on the cloud even with a solid EULA, and laws are subject to change. Please offload this burden back to…
3 votes -
Support for windows certificate store
Currently, SQL prompt doesn't support the windows certificate store like most applications do. The only way to work around that currently is to simply trust all certificates which is inconvenient (having to set this across potentially hundreds of server connections) and a security gap.
SQL prompt should either provide an option to leverage the certificates. Currently, if a blanket trust is not provided, SSMS and SQL in general will work fine, but SQL prompt will cease to function, since the application (visual studio, SSMS) will connect correctly, but SQL prompt will not.
1 vote -
Add "Clean install" option during installation
Add "Clean install" checkbox with appropriate warnings and option to back up styles and tab history where the user can specify and/or change the suggested backup location by default. Offer an easy option (inside menu?) to restore from the backup once installed. Take a look at Visual Studio editor options can be exported (backed up to a file) and subsequently restored later.
Also, take a look at nVidia, AMD Radeon (formerly ATI) and perhaps Intel network card driver installers as an example for "clean install".
1 vote -
Generate C#/VB.NET class
It would be nice to have the ability to right-click on a table or stored procedure and generate a C# or VB.NET class from the table structure or stored procedure results that could be used in a development solution.
3 votes -
Full support for Azure SQL Managed Instance in SQL Prompt
SQL Prompt should fully support Azure SQL Managed Instances. This includes offering suggestions for all objects (such as system functions, tables, views, etc) which are usable in Managed Instances. For example, CURRENTTIMEZONE and CURRENTTIMEZONE_ID (which were recently implemented in SQL Prompt, but only for Azure SQL Database). All other functions I've tried seem to be working fine, but it would be nice to know that Azure SQL Managed Instance is officially supported by SQL Prompt.
8 votes -
Support for MS Dataverse / CDS
Add support so SQL Prompt will work in SSMS when connected to MS Dataverse / CDS (Common Data Service - Dynamics really).
Right now, it fails since the (meta)data exposed probably isn't quite as complete as on a "full-scale" SQL Server database
4 votes -
Visual Studio Preview Support
Please add support for Visual Studio Preview versions. We frequently work in those and SQL Prompt Pro specifically is not available.
7 votes -
Support SSDT for SQL Prompt
Create Install Package for installing SQL Prompt in SSDT. SSDT is a VS shell, so Prompt should be easily incorporated.
5 votes -
Schema Folders
Please introduce Schema-Folders in SQL-Server Object Explorer
as shown in
https://github.com/nicholas-ross/SSMS-Schema-FoldersOr make SQL-Prompt working together with
https://github.com/nicholas-ross/SSMS-Schema-Folders.The Features "Show in Object Eplorer" and "Skript Object as ALTER"
don't work together with Nicolas Ross' Schema Folders3 votes -
Schema Folders
Please introduce Schema-Folders in SQL-Server Object Explorer
as shown in
https://github.com/nicholas-ross/SSMS-Schema-FoldersOr make SQL-Prompt working together with
https://github.com/nicholas-ross/SSMS-Schema-Folders.The Features "Show in Object Eplorer" and "Skript Object as ALTER"
don't work together with Nicolas Ross' Schema Folders0 votes -
Fix this bug with your software and Visual Studio 2017
Have it not break Visual Studio 2017 even when selecting that you don't want it to be integrated with it.
The problem is that we could no longer get latest version after installing your software and then rebooting. Here is an email that I just sent to a group of people that have had the issue for at least a week before we narrowed the problem...Guess what!?
We found what caused the issue, can reproduce it, and fix it.
The issue is with Redgate’s software, specifically SQL Prompt for us.
This is the reason that John never had the…6 votes -
Create package for Visual Studio Code
Visual Studio Code has the ability to connect to SQL servers and execute scripts. It would be nice if SQL Prompt was available for Code as well.
84 votes
- Don't see your idea?