SQL Complete causing failed logins when DB is restoring
Posted: Mon 25 Nov 2013 13:40
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!)
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!)