Merge pull request #17 from happyadam73/feature/remove-sql-tags-in-response

Remove ```sql tags from response

Author: happyadam73

sql/TSqlChatGPT.sql

@@ -8,6 +8,7 @@
 -- Revision History:    1.1 (Error handling improved, and no longer need to find/replace APIM URL)
 --                      1.2 (AWB, 17/08/2023) - Added natural query language support with the usp_ExecuteNaturalQuery stored procedure
 --                      1.3 (AWB, 23/08/2023) - Bugs fixes and support for Views
+--					    1.4 (AWB, 27/05/2024) - GPT models returning ```sql tags even if prompted otherwise
 --	
 -- 
 -- DISCLAIMER: 
@@ -236,6 +237,10 @@ BEGIN
 		IF @response IS NULL
 			THROW 50000, 'It was not possible to extract a message response from the OpenAI Chat API', 1;
 
+		-- Remove any preceding ```sql and ``` from the response - this seems to be a change in behaviour of
+		-- some GPT models (such as 3.5 Turbo) even if the system/user prompt explicitly forbids this
+		SET @response = REPLACE(REPLACE(@response, '```sql', ''), '```', '');
+
 		-- Print response if required (and not in debug mode)
 		IF @print_response = 1 AND @debug = 0
 			EXEC [dbo].[usp_PrintMax] @response;

sql/TSqlChatGPTForAOAI.sql

@@ -9,6 +9,7 @@
 --                      1.1 (AWB, 16/08/2023) - default model is 16K token version (available in UK South), and amend system message to support CODEONLY response
 --                      1.2 (AWB, 17/08/2023) - Added natural query language support with the usp_ExecuteNaturalQuery stored procedure
 --                      1.3 (AWB, 23/08/2023) - Bugs fixes and support for Views
+--					    1.4 (AWB, 27/05/2024) - GPT models returning ```sql tags even if prompted otherwise
 --	
 -- 
 -- DISCLAIMER: 
@@ -263,6 +264,10 @@ BEGIN
 		IF @response IS NULL
 			THROW 50000, 'It was not possible to extract a message response from the Azure OpenAI Chat API', 1;
 
+		-- Remove any preceding ```sql and ``` from the response - this seems to be a change in behaviour of
+		-- some GPT models (such as 3.5 Turbo) even if the system/user prompt explicitly forbids this
+		SET @response = REPLACE(REPLACE(@response, '```sql', ''), '```', '');
+
 		-- Print response if required (and not in debug mode)
 		IF @print_response = 1 AND @debug = 0
 			EXEC [dbo].[usp_PrintMax] @response;