SQL Templates and Code Snippets in SSMS and SQL Prompt
Phil Factor explains the uses and limitations of native SSMS templates and snippets, and then demonstrates the extra versatility that SQL Prompt snippets provide.
2021-03-22
sql prompt
Reusing Query Results in SSMS
Every time you need to reuse the query results from SSMS, for example to populate another table, or to search for matching rows in another table, it will inevitably mean a lot of manual tweaking to the get the results into the right format. Louis Davidson uncovers three SQL Prompt gems that can remove all this pain.
2021-03-16
Sharing SQL Code Snippets with Coworkers, The World and Yourself
Louis Davidson explains how he manages and shares several different sources of SQL Prompt code snippets, in a single Snippet library, using Dropbox and source control.
2020-12-23
More Gems from the SQL Prompt Treasure Chest
Become the captain of your SQL Prompt ship by embarking on a voyage of discovery through the hidden treasures of the tool. You'll uncover features of the unknown that will enable you to write, format, analyze and refactor your SQL effortlessly. Join this webinar on December 16th to find out more.
2020-12-15
More Gems from the SQL Prompt Treasure Chest
Join Microsoft MVP Grant Fritchey and Redgate's Owen Standage on a journey through the hidden treasures of SQL Prompt. Discover features of the unknown that will enable you to write, format, analyze and refactor your SQL effortlessly.
2020-12-10
SQL Snippets Galore, Added to SQL Prompt
Imagine having at your fingertips all the metadata queries you need to explore your SQL Server databases and then, a few clicks later, all your diagnostic queries to troubleshoot their performance. Phil Factor demonstrates how it can be done, by storing each set of snippets in a standard JSON collection and using PowerShell to convert them to SQL Prompt snippet files.
2020-11-25
Managing Cross-Database Object References
Phil Factor explains cross database and cross-server references, how to find them in your code, and when it's better to avoid hard-coding these references and use synonyms instead.
2020-11-20
Creating a SQL Code Snippet in SQL Prompt and SSMS
Phil Factor's "getting started" guide for turning all your trusted and most frequently used queries into SQL code snippets.
2020-11-12
Questions about SQL Prompt you were too shy to ask
Phil Factor answers some questions you've been itching to ask about SQL Prompt, covering ranked code completion suggestions and auto-fixing SQL code smells, and suggesting where in the tool to find other nuggets of hidden treasure.
2020-11-06
SQL IntelliSense and Autocomplete in SSMS
Phil Factor reviews the major features of SSMS IntelliSense and autocomplete and then explains how SQL Prompt fills in the gaps, and how to use to use the two in tandem to 'get the best of both worlds'.
2020-11-02
Blogs
Flyway Tips: AI Deployment Script Descriptions
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
A New Word: Fawtle
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
Post-quantum key exchange – Insurance policy for your packets
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Forums
Where Your Value Separates You from Others
Comments posted to this topic are about the item Where Your Value Separates You...
Fixing the Error
Comments posted to this topic are about the item Fixing the Error
T-SQL in SQL Server 2025: Encoding Functions
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Question of the Day
Fixing the Error
On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:
SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error? See possible answers