SQL Prompt 6.3 beta (Now closed)

• 
  Option to turn OFF bracket-matching, please?
  
  I find that SSMS Intellisense limited to code blocks and bracket-matching works extremely well with SQL Prompt. I wouldn't like to see the two products argue over who will highlight a bracket, or not.
  
  Thanks.

  PDinCA January 24, 2014 18:22

  - 0 +
• 
  Hi Stephen,
  
  I don't think they argue over who gets to highlight a parenthesis, if you do notice any issues please let us know and we'll fix them.

  Aaron L January 27, 2014 06:58

  - 0 +
• 
  When formatting SQL XML statement like the following with the XML method "nodes" on my computer, nodes becomes capitalized, and this capitalization causes the query to fail. Also, I noticed that formatting puts a space between the "T" and "(x)". I don't remember that happening in previous versions.
  
  It should be:

  SELECT  T.x.value('./@Value1', 'INT'), T.x.value('./@Value2', 'INT')
  FROM    @XMLVariable.nodes('RawData/RawDataRecord') AS T(x)
  

  
  After formatting:

  SELECT  T.x.value('./@Value1', 'INT'), T.x.value('./@Value2', 'INT')
  FROM    @XMLVariable.NODES('RawData/RawDataRecord') AS T (x)
  

  
  I never had problems with the node keyword or its alias before the beta, so I think it might be a bug. Can you please have someone look into it?
  
  Thanks.

  JBSandhills January 28, 2014 18:32

  - 0 +
• 
  Hi JBSandhills,
  Thanks for reporting this - I can recreate the "nodes" being uppercased and will look into a fix for you.
  
  For the space between the T and the (x) I think that it might have always been like that (I just gave it a try 6.2 and 5.3). Is this something you'd want changed?

  Aaron L January 29, 2014 04:59

  - 0 +
• 
  Hi Aaron,
  It would be nice to have the space removed because it looks a bit strange; however, it's not the end of the world if this feature has to come sometime later. As long as the NODES issue is fixed by stable release, my coworkers and I will be very happy.

  JBSandhills January 29, 2014 09:43

  - 0 +
• 
  The xml casing should be fixed for you in 6.3.0.95.

  Aaron L January 30, 2014 09:04

  - 0 +
• 
  Microsoft SQL Server Management Studio 11.0.3401.0
  SQL Prompt Pro 6.3.0.102
  SQL Search 1.1.9.57
  SSMS Tools Pack 2.7.2.0
  
  Instant crash after typing number after GO. In SSMS you can specify how many times should SSMS repeat statement.
  

  PRINT 'You will see this message 10 times'
  GO 10
  

  
  This works fine with SQL Prompt 6.2.
  
  Edit: Yay, just paste example in SSMS and...

  Mr.DiGi February 06, 2014 08:13

  - 0 +
• 
  Hi Mr.DiGi,
  
  I'm really sorry you've encountered this crash but thank you for reporting it. I can recreate it here and will look into a fix for you, hopefully I'll have a new build out shortly.
  
  Thanks,
  Aaron.

  Aaron L February 06, 2014 09:26

  - 0 +
• 
  I've just uploaded 6.3.0.121 which should have a fix for this crash. Thanks again for reporting it!

  Aaron L February 06, 2014 12:05

  - 0 +
• 
  No problem, thanks for quick fix.

  Mr.DiGi February 07, 2014 04:33

  - 0 +
• 
  More (minor) bugs - User defined table type related:
  
  - Select in Object Explorer is not working for table type
  - column names from table type are not listed (maybe this didn't work with previous version too)
  - we have custom table type with "Value INT" column. After using column "Value" in join all database object/names disappears from SQL Prompt (only snippets are listed).
  
  demo:
  

  CREATE TYPE [dbo].[IntTable] AS TABLE
  (
  	[ID] [int] IDENTITY(1,1) NOT NULL,
  	[Value] [int] NULL
  )
  GO
  
  DECLARE
  	@x dbo.IntTable
  
  SELECT
  	1
  FROM
  	@x AS X
  	INNER JOIN sys.objects AS O ON O.object_id = X.Value
  	INNER JOIN <no hint here>
  

  
  Just changing "O.object_id = X.Value" to (invalid) "O.object_id = X.ValueZZZ" brings SQL Prompt back.
  
  Edit: Or we can use O.object_id = X.[Value] - maybe because XML type .value, .nodes hacks?

  Mr.DiGi February 07, 2014 05:50

  - 0 +
• 
  Thanks for reporting these, I can recreate them here and we're looking into fixes for them.
  
  I think you are right about the value being mixed up with the xml type value and so Prompt is wrongly expecting parentheses and parameters, which results in it not giving you the correct suggestions.

  Aaron L February 07, 2014 11:12

  - 0 +
• 
  Hi Mr DiGi,
  Just to let you know, the bugs you mentioned in your last post should be fixed in 6.3.0.188.
  
  Thanks,
  Aaron.

  Aaron L February 28, 2014 05:37

  - 0 +
• 
  Awesome, thanks for fixes.
  
  OT: Is there any way to log/debug Qualify object names call? It just hang for our db (almost since beginning).
  
  No error in "....\AppData\Local\Red Gate\SQL Prompt 6\sqlpromptlog-yyyymmdd-hhmmss.log"

  Mr.DiGi March 05, 2014 16:34

  - 0 +
• 
  Attributes used to come first for WHERE clauses - now they are last and that's highly counterproductive. I get other table then function names before columns. Is it just me? Using the 188 build, win8.1 x64, SQL2012EE

  PDinCA March 06, 2014 01:30

  - 0 +
• 
  Hi PDinCA,
  I'm having difficulty recreating your issue - I always get columns suggested first on a where clause. Would it be possible to get a script or a screenshot of where this is happening for you?
  
  Mr.DiGi, Unfortunately I don't think there's enough logging in the current build to help figure out where qualify object names is going wrong. Does it hang every time for you? Even on older, non-beta builds?

  Aaron L March 06, 2014 06:11

  - 0 +
• 
  Yesterday's script:

  INSERT INTO dbo.t_company_custom_def
       ( custom_id
       , custom_company_id
       , custom_xml
       , update_date
       , update_by
       )
  SELECT @NewID
       , 30
       ,[custom_xml]
       , '20140305 15:45'
       , 'me'
    FROM [xcp_ref].[dbo].[t_company_custom_def] ccd
   WHERE co
  

  First off, having completed the WHERE and a space, it gave me ccd, the alias, as expected, and correct. I typed c and the ccd alias reamined at the top, followed by columns, so I typed an o, to get to "WHERE co" as in the code above. That's when the whole list changed to a list of f(x) functions, headed by COALESCE, then CONTAINS, then a bunch of tables (I have them listed by schema), then a slew of sys.functions, and I don't see the "custom_COmpany_id" (in the enlarged pop-up) that I expected my CO typing to bring to the top of the list. SQL Prompt at this point becomes useless for rapid code completion.
  
  I would really like to send you a SnagIt or Snip, but Windows8.1 has completely destroyed my ability to use them. I hope you can create a simple table like the above, and reproduce the problem...
  
  Failing that, a remote diagnostic session would be fine by me.

  PDinCA March 06, 2014 17:17

  - 0 +
• 
  Hi PDinCA,
  I just gave your script a try and I think this behavior might be by design. Prompt will display any objects matched by the prefix first (COALESCE, CONTAINS etc all start with CO) followed by any partial matches.
  
  I get the column listed much further down as it's not considered that "good" a match yet:
  
  
  To get a better match against the columns you should be able to type the first letter or two of each word (eg. Typing "cu_co", "cco" or even "_co" will give a better match against custom_company_id)
  
  Edit: as of 6.3.0.240 the columns should be at the top of the partial matches list, objects matched by a prefix are still first however.

  Aaron L March 07, 2014 06:25

  - 0 +
• 
  I must admit to being surprised by the volume of what I will call "noise" listed above potential columns that are partially matched.
  
  Thinking about the context of the SQL Prompt suggestions, when one is writing a SQL WHERE clause, how frequently is a column in a FROM clause the actual subject of the WHERE versus some obscure system function, another table name (huh?), or a function? I'd suggest that in excess of 95% of the time the COLUMN is what is wanted... It is acknowledged BAD PRACTICE to use functions in WHERE clauses anyway, or so I believe.
  
  I'm out of votes on SQL Prompt (two logins' worth), so may I here suggest:
  
  Provide an option to "always list columns in suggestion lists, even partial matches, above any functions of any kind".
  
  In over 25 years of coding SQL, I can safely say the number of times I want a built-in or sys. function as the FIRST artifact after my WHERE is 0.05% of the time, or less!
  
  Doesn't "columns first" simply just make sense? Or maybe I really am missing something...

  PDinCA March 11, 2014 13:20

  - 0 +
• 
  Hi PDinCA,
  Could you give 6.3.0.252 a try and see if that's closer to what you'd prefer? (We normally sort by prefix/partial match and then the object type, build 252 should reverse this so columns and aliases are kept at the top for the WHERE clause)

  Aaron L March 18, 2014 10:18

  - 0 +
• 
  Thanks Aaron, installed and makes a lot more sense. Tried several partial matches on wide tables and everything looks good. Appreciate the swift turnaround.

  PDinCA March 18, 2014 19:13

  - 0 +

Add comment

Please sign in to leave a comment.