How can we help you today? How can we help you today?
shand_obs
That seems so odd. I could swear it works fine in my SSDT project, at least it was before the update. We use Azure SQL, but I'm not often connected to the database when I'm working. SQL Prompt's autocomplete provides fuzzy search suggestions. I can type "mct" for example, and if I have a table called "MyCrazyTable", SQL Prompt suggests it. SQL Prompt also automatically puts square brackets around my selections. The native intellisense only completes square brackets if I remember to type one at the start, but I got so accustomed to the shortcuts from SQL Prompt that I find myself frequently omitting the opening square bracket. Finally, SQL Prompt suggests keywords, so writing a MERGE becomes faster not having to remember all of the fluent crap that has to go in there. I will go vote on this suggestion, but I really want to know how this ever worked for me before. My workflow hasn't changed and something I found really useful just disappeared. EDIT: SQL Prompt also auto completes my schema names. I don't have to start typing a schema name; I can just start typing a table name and when I choose the suggestion it auto inserts the schema prefix for me. With the native intellisense I don't even get any of my table names in the suggestions until I type the schema prefix. / comments
That seems so odd. I could swear it works fine in my SSDT project, at least it was before the update. We use Azure SQL, but I'm not often connected to the database when I'm working. SQL Prompt's au...
0 votes
8.2.4.2825 Core I do have a SSDT project in my solution, but I much prefer the SQL Prompt autocomplete over the SSDT autocomplete. Is there any work around for this? What's the reason SQL Prompt is disabled for SSDT? / comments
8.2.4.2825 Core I do have a SSDT project in my solution, but I much prefer the SQL Prompt autocomplete over the SSDT autocomplete. Is there any work around for this? What's the reason SQL Prompt is...
0 votes