SQL Prompt 9 - now available

• 
  Hi Jamie.
  
  I'm giving this a go now.
  
  I cant seem to find how to switch on the 'Issue Details' pane as shown in the screenshot above?
  
  Any suggestions?
  
  I'm using SSMS 2012.
  
  cheers
  Ben
  
  Microsoft SQL Server Management Studio 11.0.3000.0
  

  ben_b November 28, 2017 11:42

  - 0 +
• 
  Sorry, i've just found it. Click on the green underlined keyword (don't just mouse-over) and press control.
  
  new functionality looks good

  ben_b November 28, 2017 11:45

  - 0 +
• 
  Just installed it. Will let you know what I think.

  unclebiguns November 28, 2017 18:44

  - 0 +
• 
  A couple of comments about the new Code Analysis.
  

  1. Seems to work pretty well, but when there is code analysis message, it keeps the normal SQLPrompt Intellisense pop-ups from working. So if you use a stored procedure and violate the named parameter use rule you can't get the definition of the stored procedure.
  2. The "Schema name for table or view is not specified" rule should not apply to temp tables. It looks like this is only an issue if you add an index to a temp table the index definition violates the rule. Like this:
     CREATE TABLE #test(colA CHAR(1) NOT NULL, colB CHAR(1) NOT NULL);
     CREATE NONCLUSTERED INDEX IX_test ON #test (colA);
     
     SELECT T.colA, T.colB FROM #test AS T

  unclebiguns November 30, 2017 20:45

  - 0 +
• 
  Thanks Jack, i'll pass that on to the team.

  Jamie W December 01, 2017 08:30

  - 0 +
• 
  Awesome update.

  nsundararajan December 01, 2017 16:35

  - 0 +
• 
  Is there any more documentation or supporting articles for rule SC003 - There should be no USE statement in batch?
  
  I understand flagging context switching and USE statements in the middle of a batch, but it also gets flagged when it's the first statement and only used at the beginning of a script. Including this has saved me a bunch of times, so I want to understand why this is discouraged.
  
  Thanks!

  Cathrine December 04, 2017 20:14

  - 0 +
• 
  This looks really neat. Can't wait to give it a try!

  BobPusateri December 05, 2017 04:37

  - 0 +
• 
  Hi Cathrine
  
  We don't have anything further on file at the moment, so we've asked Oleksii (SQL Code Guard creator) if he can provide some more info - will send on when we get a reply.
  
  Thanks
  
  Jamie

  Jamie W December 05, 2017 10:47

  - 0 +
• 
  Further to the above, here's what Oleksii says:
  
  "The primary reason for such rule is to avoid hardcoded (specific) database name - i assume that each SQL script will be run under context of previously selected database.
  
  "E.g. - when installing any product which requires database, at the very first step you enter database name and later installation package will create database with custom name you entered and run script within this database.
  
  "If (for some reason) you've left with something like "USE MyTestDatabase" in your script then the whole installation will fail (this is bad but not fatal) or you may occasionally change the database context to another existing database.
  
  "So i think this is not so good to have USE in script file."
  
  Let me know if that helps or if you need further info.
  
  Thanks
  
  Jamie
  

  Jamie W December 05, 2017 11:00

  - 0 +

Add comment

Please sign in to leave a comment.