Bug in finding invalid objects

scollisscollis Posts: 32 Bronze 3
edited June 24, 2015 7:22AM in SQL Prompt
Just doing a scan for invalid objects. There are 1,545 to check, and it gets to 980 and stops with "Login failed".

Now probably that is the cause of my problem, in that the object it's trying to check nobody has permissions on. However because of that login failed, I can't see which object is causing the problem.

Can we have a fix so that if it gets a login problem hitting a specific object, it will report that as being the reason for the object being invalid, rather than stopping with a login problem screen which (in this case) is somewhat less than helpful?

Ta muchly :)

Comments

  • Sergio RSergio R Posts: 610 Rose Gold 5
    Hi zippy72,

    So that I can be sure we're on the same wavelength are you using the Find Invalid Objects feature in SQL Prompt?

    Thank you,
    Sergio
    Product Support Engineer
    Redgate Software Ltd
    Please see our Help Center for detailed guides on how to use our tools
  • scollisscollis Posts: 32 Bronze 3
    Yes, it's SQL Prompt 6.5.0.330
  • Anu DAnu D Posts: 876 Silver 3
    This post is created to merge the SQL Prompt topic which was created in Source control forum instead of Prompt forums
    Anuradha Deshpande
    Product Support
    Redgate Software Ltd.
    E-mail: support@red-gate.com
  • Sergio RSergio R Posts: 610 Rose Gold 5
    Hi zippy72,

    I am unsure at this moment whether this is a bug as I have been unable to replicate it in our lab.
    I will get in touch with you through our support system to get more details to better assess the situation.

    Thank you,
    Sergio
    Product Support Engineer
    Redgate Software Ltd
    Please see our Help Center for detailed guides on how to use our tools
  • scollisscollis Posts: 32 Bronze 3
    Hi Sergio,

    I didn't get a "report this error" box - usually I use that and don't bother with anything else. In this case, I didn't.

    I was going to record you a video so you could see the behaviour - and today, it's working. So something has changed with the new version (I'm on frequent updates and can't remember when the last one was) or something has changed with the security settings on the database.

    Either way, you might as well close this one off and if I get it again I'll record a video so you can see the behaviour.

    Thanks for your help! :)
Sign In or Register to comment.