SQL Prompt 7 beta (now closed)

• 
  The download link for 6.6.0.189 beta does not work for me here. Could you help to check please?

  ogrishman June 28, 2015 14:11

  - 0 +
• 
  Hi ogrishman,
  
  The link seems to be OK for me, could you try again and see what happens?
  
  Best regards,
  
  David

  David Priddle June 29, 2015 02:40

  - 0 +
• 
  Hi,
  
  Just installed the 6.6 beta. There are no shortcuts now (such as ctrl+K+Y for formatting). Should that be there still?
  
  cheers
  
  Matt

  mjharper July 01, 2015 15:30

  - 0 +
• 
  Hi Matt,
  
  Yes there should still be shortcuts. Which version of the environment (SSMS or VS) are you seeing this in?
  
  Are they still missing if you restart the environment?
  
  Best regards,
  
  David

  David Priddle July 02, 2015 07:13

  - 0 +
• 
  Hi
  
  I'm using SSMS (13.0.300.44). A reboot of the machine seems to have sorted it out!
  
  Thanks,
  
  Matt

  mjharper July 02, 2015 07:55

  - 0 +
• 
  Hi Matt,
  
  Thanks for letting me know, I'm glad it's sorted!
  
  Best regards,
  
  David

  David Priddle July 02, 2015 08:22

  - 0 +
• 
  Hi,
  if "Load suggestions for synonyms/Load referenced databases" are enabled and user does not have permissions for some underlied objects then it is flooding error messages to the log for every synonym that user does not have permissions for.

  sdks July 23, 2015 04:40

  - 0 +
• 
  Hi sdks,
  
  If there's a permissions error when retrieving an object then it sounds like it's doing the correct thing by logging it. Could you email your log to aaron.law@red-gate.com and I'll have a look, perhaps we could reduce the amount of logging around this error.
  
  Thanks,
  Aaron.

  Aaron L July 24, 2015 04:21

  - 0 +
• 
  There is no point to email. It is the same line repeated a lot of times:

  2015-07-22 07:46 xxx.xxx.xxx.xxx Login failed for user 'DOMAINUSER'. Reason: Could not find a login matching the name provided. [CLIENT: xxx.xxx.xxx.xxx]
  2015-07-22 06:33 xxx.xxx.xxx.xxx Login failed for user 'DOMAINUSER'. Reason: Could not find a login matching the name provided. [CLIENT: xxx.xxx.xxx.xxx]
  2015-07-22 05:51 xxx.xxx.xxx.xxx Login failed for user 'DOMAINUSER'. Reason: Could not find a login matching the name provided. [CLIENT: xxx.xxx.xxx.xxx]
  2015-07-22 05:25 xxx.xxx.xxx.xxx Login failed for user 'DOMAINUSER'. Reason: Could not find a login matching the name provided. [CLIENT: xxx.xxx.xxx.xxx]

  
  Do not look to time. Mainly it differs milliseconds and in my case it generates about 30 records in 1 second.
  
  And the query causing that (most probably) is:

  SELECT
  SCHEMA_NAME(s.schema_id) AS [Schema],
  s.name AS [Name],
  s.object_id AS [ID],
  N'' AS [BaseDatabase],
  N'' AS [BaseObject],
  N'' AS [BaseSchema],
  N'' AS [BaseServer],
  
                                                  CASE OBJECTPROPERTYEX(s.object_id,'BaseType') 
                                                                  WHEN N'U' THEN 1 
                                                                  WHEN N'V' THEN 2 
                                                                  WHEN N'P' THEN 3 
                                                                  WHEN N'FN' THEN 4 
                                                                  WHEN N'TF' THEN 5 
                                                                  WHEN N'IF' THEN 6 
                                                                  WHEN N'X' THEN 7 
                                                                  WHEN N'RF' THEN 8 
                                                                  WHEN N'PC' THEN 9 
                                                                  WHEN N'FS' THEN 10 
                                                                  WHEN N'FT' THEN 11 
                                                                  WHEN N'AF' THEN 12 ELSE 0 END
                                  AS [BaseType],
  s.base_object_name AS [BaseObjectName]
  FROM
  sys.synonyms AS s
  ORDER BY
  [Schema] ASC,[Name] ASC
  

  
  
  so, everytime I am using synonym intellisense generates a lot of errors. I am not talking about the situation when I am trying to access object I do not have access to, it is just scanning all synonyms and for some of them I do not have permissions.

  sdks July 24, 2015 10:01

  - 0 +
• 
  Hi sdks,
  
  I was more interested in which of our loggers is logging the error rather than the error itself. This should be listed in the log file under SQL Prompt->Help->Show Log. Just before the error message it should have the logger name. What is that?
  
  Thanks,
  Aaron.

  Aaron L July 27, 2015 06:06

  - 0 +
• 
  Hi,
  
  Is there a way to disable the 'Quick Options' menu (I don't know the correct terminology for it) that now comes up when you highlight a selection?
  
  I use ClipJump as a clipboard manager, and I'm finding that when I press Ctrl+V to paste it's pasting it into this new menu's search box rather than in place of the text I had selected.
  
  If I disable ClipJump and use the Windows copy and paste it works fine, and I know SSMS now has a clipboard ring, but it's not quite as full featured!
  
  The only option that I might miss from the new menu is Unformat SQL, but that's only because I can't see it in any other menu. For everything else I use keyboard shortcuts or the context menu.
  
  I think the menu is a good idea, it just doesn't seem to function as intended when used with ClipJump at the same time!
  
  
  Thanks,
  Steve

  S Saunders July 31, 2015 04:45

  - 0 +
• 
  Hi Steve,
  
  Thanks for letting us know about Clipjump - it must handle keyboard input in a different way from SSMS/VS so we'll see if we can get our popup to work nicely alongside it.
  
  In the meantime you can turn the popup off by editing the xml file under %localappdata%Red GateSQL Prompt 6RedGate_SQLPrompt_CommonUI_Options_UIOptions.xml and setting <EnableSurroundWithPopup> to False.
  
  We're hoping to add a few more features to the popup soon (such as "commarise") and it's also used for "surround with" snippets containing $SELECTEDTEXT$, so ideally we'd like to get it working rather than disabling it.
  
  Thanks,
  Aaron.

  Aaron L July 31, 2015 05:20

  - 0 +
• 
  Thanks Aaron,
  
  That's hidden it for now, I look forward to it working as intended in future!
  
  Clipjump probably does handle keyboard input differently, it's an AutoHotkey script that over time has grown and been wrapped in its own .exe.
  
  
  Cheers,
  Steve

  S Saunders July 31, 2015 09:52

  - 0 +
• 
  Hi Steve,
  
  We think we've fixed this in the latest beta build (for both Clipjump and AutoHotKey). Could you give it a try and let us know if that fixes it for you?
  
  Thanks,
  Aaron.

  Aaron L August 05, 2015 09:00

  - 0 +
• 
  Hi Aaron,
  
  Sorry, I didn't see your reply until today!
  
  I've just installed the version 7 beta, I've not tested AutoHotKey thoroughly but what I have appears to work fine.
  
  I'm still experiencing the same behaviour from Clipjump however
  
  
  Separate to that, after installing 7.0 my snippets from 6.x weren't brought forward; this isn't an issue for me as I've just copied them across from the 6.x folder but I thought I'd mention it in case it wasn't intentional!
  
  
  Cheers,
  Steve

  S Saunders August 10, 2015 10:24

  - 0 +
• 
  Hi Steve,
  
  We're having difficulty getting the same behaviour out of Clipjump with the latest build, it seems to work on our dev machines and VMs so I'm wondering if there's something extra that we're missing. Just to check, which version of Windows and SSMS are you running? Is there anything else that you can think of that might be different? (eg. if one of the programs is being run as a different user)
  
  For the snippets we should be upgrading them but we're overwriting the defaults with some new ones as we've tweaked a few to include things like $SELECTEDTEXT$ so if you had customized them then they might have been overwritten. I'll see if we can just upgrade the default snippets that have changed to help avoid the confusion.
  
  Thanks,
  Aaron.

  Aaron L August 11, 2015 05:18

  - 0 +
• 
  Hi Aaron,
  
  I'm running Windows 7 (though may soon be upgrading to 10), SSMS 2016 CTP2, and Clipjump v12.
  
  My Clipjump.exe file has its Privilege Level set to 'Run this program as an administrator'.
  
  That makes sense regarding the snippets.
  
  
  Cheers,
  Steve

  S Saunders August 12, 2015 07:07

  - 0 +
• 
  Thanks for the extra details Steve!
  
  We've done a little more testing in Win7 and it looks like if Clipjump is run as an administrator then running SSMS as an admin should fix the issue.
  
  Thanks,
  Aaron.

  Aaron L August 12, 2015 09:07

  - 0 +
• 
  I can confirm that running SSMS as an administrator as well does fix this issue, thanks!
  
  
  Thanks,
  Steve

  S Saunders August 12, 2015 11:21

  - 0 +

Add comment

Please sign in to leave a comment.