SQL Prompt 7.2 beta (now closed)

• 
  Hello,
  
  This release seems to have issues with linked servers it didn't have before. None of my linked servers seem to get intellisense and failures pop up whenever it attempts.
  
  Also, this:
  

  	-- Ensure valid store number
      IF NOT EXISTS ( SELECT  [tblStores].[StoreNum]
                      FROM    [Corpmaster]..[tblStores]
                      WHERE   [tblStores].[StoreNum] = @StoreNum )
      BEGIN
          THROW 60000, N'Invalid store number passed.', 1;
      END;	
  

  
  The "THROW" statement is red wavy underlined, and the "END;" semi-colon is underlined red. After I reformat SQL it goes away, then re-appears a few seconds later.
  Image: http://imgur.com/9houGbj

  jsreynolds1 March 22, 2016 17:55

  - 0 +
• 
  I have a good log I would like to send to someone and not post here. Any takers?

  jsreynolds1 March 22, 2016 18:44

  - 0 +
• 
  Hi John,
  
  Thanks for your post! please email me the log file: aaron.law@red-gate.com and i'll have a look into what's going wrong.
  
  Thanks,
  Aaron.
  
  UPDATE: We've been able to track down and fix a potential cause. Could you try grabbing the latest beta build to see if that helps?

  Aaron L March 23, 2016 05:15

  - 0 +
• 
  Aaron,
  
  I thought I'd try the latest beta first, and sure enough it did fix the issue with linked servers.
  Also, the wavy lines under the THROW statement are gone. Things seem to be back to normal.
  
  Thanks much,
  
  John

  jsreynolds1 March 23, 2016 11:55

  - 0 +
• 
  Thanks for giving it a try - I'm glad to hear everything is working again!

  Aaron L March 23, 2016 11:59

  - 0 +
• 
  Stopped working in SQL Server 2016 Preview.

  kbraltodoteu April 12, 2016 08:11

  - 0 +
• 
  Hi kbraltodoteu,
  
  Do you have any more information on what doesn't work for you?
  
  The latest beta supports SSMS March 2016 Preview Refresh and not the older SSMS 2016 previews, so you might need to upgrade if you'd like to continue using Prompt in SSMS2016. Older versions of SSMS (2014, 2012 etc) should continue to work as before.
  
  Thanks,
  Aaron.

  Aaron L April 12, 2016 08:24

  - 0 +
• 
  I was using the 7.2.0.212 version, but when updated to version 7.2.0.241 nothing worked, formatting, intellisense, and all options are disabled in SQL Prompt menu, except the Options and Help, and when it comes into options by clicking any option it closes the form. My version of SQL Server is 13.0.12000.75

  kbraltodoteu April 12, 2016 08:33

  - 0 +
• 
  Hi kbraltodoeu,
  
  You'll need to upgrade your SSMS to the March 2016 Preview Refresh (13.0.13000.55): https://msdn.microsoft.com/en-us/library/mt238290.aspx
  
  Thanks,
  Aaron.

  Aaron L April 12, 2016 08:37

  - 0 +
• 
  It worked ... Nice work ... Congratulations.
  
  Thank you so much.

  kbraltodoteu April 12, 2016 08:59

  - 0 +
• 
  version 7.2.0.241
  
  WAIT ON THIS - I MAY BE WRONG. I will come back and edit or delete based on more findings.
  
  Beginning of a stored procedure (nothing odd in the creation part), I get this.
  
  

      SET NOCOUNT ON;
  
      DECLARE @ErrorMessage NVARCHAR(2048);
  
  	-- Let's just get this awkwardness out of the way up front;
  	-- Is there (still) a product for the store available, or did 
  	-- someone else on the front end rip it out from under the 
  	-- current user?
      IF NOT EXISTS ( SELECT  *
                      FROM    [Products]
                      WHERE   [Products].[ProductID] = @ProductID )
      BEGIN
          SET @ErrorMessage = 'Product no longer exists.';
          ;
          THROW 60000, @ErrorMessage, 1;
      END;	
  

  
  But the Products table has ProductID as a column. Many squiggly red lines below this one too. Here is the start of the procedure just in case you need that. Note that everything runs fine in the proc, there are no syntax errors anywhere.
  

  SET ANSI_NULLS ON;
  GO
  SET QUOTED_IDENTIFIER ON;
  GO
  ALTER PROCEDURE [dbo].[fe_UpdateOnInventory]
      @StoreNum CHAR(3),
      @ProductID INTEGER,
      @ProductName NVARCHAR(4000),
      @PDSID INT,
      @Status BIT
  AS /*
  

  jsreynolds1 April 15, 2016 20:20

  - 0 +
• 
  Hi John,
  
  There's a chance this is actually SSMS itself adding the red squigglies if you've got underline errors turned on in the SSMS options:
  
  If you disable that option do the squigglies still appear?
  
  Thanks,
  Aaron.

  Aaron L April 18, 2016 05:40

  - 0 +

Add comment

Please sign in to leave a comment.