SQL Complete causing failed logins when DB is restoring

[jeffk]

Hi all,

have a bit of a weird situation... Several installs of SQL Complete, and this only happens on 1 of the 2 installs.

Basically during a nightly restore of a DB (takes 2 hours) we get constant errors from that person's PC with the following error every 3 minutes exactly.

DESCRIPTION: Login failed for user 'xxx\xxxxxx'. Reason: Failed to open the explicitly specified database 'xxx'. [CLIENT: x.x.x.x]

Is there some check for updated meta data every 3 minutes or something simliar?

Both me and the other user have SQL 2012 mgmt studio opened with connections to the server in question. the only real difference is that i'm SA and the other user is not.

thanks!

Jeff

(btw: great product, beats the hell out of the native auto-complete/intellisense!)

[alexa]

We are currently investigating this issue and will answer you as soon as possible.

[alexa]

Could you please check and let us know whether the errors were thrown by SSMS or dbForge SQL Complete and provide us the screenshots of them?

If the issue was still caused by dbForge SQL Complete, could you please describe the scenario of the user actions before, during, and after performing the restore in details?

Please also provide us the full versions of dbForge SQL Complete and SQL server.

Additionally, please let us know what roles the user belongs to and what permissions it has.

You can send a reply straight to our support system at supportATdevartDOTcom, so we will keep further correspondence with you on this issue via that system.

[jeffk]

I'm having issues determining if it's dbForge or SSMS (not seeing the application text).

I'm also trying to setup some additional tests to narrow this down. I'll email you directly as soon as I get some further info.

thanks for the quick replies!

[alexa]

Thank you. We will be looking forward to your reply.