Showing incorrectly that objects are invalid

• 
  Hi Larry,
  
  SQL Prompt requires a few more permissions for Find Invalid Objects to work correctly:

  • Select
  • Execute
  • View Definition
  • Set ShowPlan
  • Set NoExec
  • Create Trigger
  • Create Procedure
  • Create View
  • Create Function

  Please let me know if this helps! If you have any more questions let me know.
  
  Best regards,
  
  David

  David Priddle April 23, 2014 06:50

  - 0 +
• 
  David,
  I am the DBA for the organization. I am the sysadm on all our database servers. I will look at the permissions at a more granular level, but as a beta tester for your product, I knew most of what you stated. I would not have posted this if I thought something else wasn't going on.
  Larry

  meklembl April 23, 2014 07:36

  - 0 +
• 
  Hi Larry,
  
  I think I may have misunderstood your post! There's a feature in SQL Prompt called Find Invalid Objects.
  
  Are you saying that you're writing a select statement in the query window, but Prompt is not providing suggestions for you?
  
  Are these newly created objects (created while you've had SSMS open)? If so, have you used Refresh Suggestions in the Prompt menu?
  
  Best regards,
  
  David

  David Priddle April 23, 2014 09:16

  - 0 +
• 
  That is correct. It happened to me again this morning. In SSMS, on the status line it shows the correct server and database, but SQLPrompt tells me that the identical database is not found in sysdatabases and then the entire sets of objects in the select statement are marked, but the query runs fine.
  
  Sorry for the slow response,

  meklembl April 29, 2014 10:32

  - 0 +
• 
  Hi Larry,
  
  Would it be possible to have a remote session with you so we can see this issue in action?
  
  Best regards,
  
  David

  David Priddle April 29, 2014 10:52

  - 0 +
• 
  Here are some free times for this week;
  Today from 3:00 - 4:00 PM EDT
  Tomorrow most of the day.
  Thurs. 1:00-4:00 PM EDT
  Friday 9:00-11:30 AM EDT

  meklembl April 29, 2014 11:10

  - 0 +
• 
  Hi Larry,
  
  Would it be OK to do it early tomorrow morning for you? Let me know when we can start and I'll send over a meeting invite.
  
  Best regards,
  
  David

  David Priddle April 29, 2014 11:30

  - 0 +
• 
  That's fine. And for upfrontness, I just checked. I am on version 6.3.0.345 and I am running SQL Search 2.0.1.8

  meklembl April 29, 2014 12:28

  - 0 +
• 
  Email address is lmeklemburg@intellicorp.net

  meklembl April 29, 2014 12:28

  - 0 +
• 
  Larry, I happen to be working on a project to change the collation of a database and fix references to that database in an uncollated DB. I've found that SQL Prompt is sensitive to those collation differences and can show an object as invalid on the uncollated server due to casing. The query will run fine, but the objects show up as invalid.
  
  It seems a little inconsistent, but I didn't dig real deep and my trial has expired. So I can't really duplicate. Just and FYI and something to look at.

  sgtmango333 May 12, 2014 10:20

  - 0 +
• 
  Hi sgtmango333,
  
  I'm one of the developers on SQL Prompt. I had a call with Larry a couple of weeks back and it looked like the problem was unlikely to us.
  
  How are the objects coming up as invalid? Through "Find Invalid Objects" or in the query window? If they are being underlined in red in the query window, that is SSMS's behaviour.
  
  If you see the collation issues again, please let us know!
  
  Best regards,
  
  David

  David Priddle May 12, 2014 10:34

  - 0 +
• 
  Thanks David. Yes it was the red underlines, so probably SSMS and not SQL Prompt.

  sgtmango333 May 12, 2014 15:04

  - 0 +

Add comment

Please sign in to leave a comment.