SCA in SSMS: "Cannot drop database "%_SHADOW" because it is currently in use"

PeterDanielsCRBPeterDanielsCRB Posts: 126 Bronze 3
in SQL Change Automation
SCA Version 4.2.20154.20409.  SSMS plugin.

Attempting to "Generate migrations".  Keep getting:

I've found the SPID connected to shadow and killed it a couple of times, but the error keeps happening.  Closing the project and re-opening doesn't help.  Restarting SSMS also not helping.  Now, I'm installing the latest update of SCA...got to reboot.  More to come....
Tagged:
· Share on Twitter

Answers

  • PeterDanielsCRBPeterDanielsCRB Posts: 126 Bronze 3
    Updating to 4.2.20161.20485 and restarting my computer seems to have fixed.  Going to leave this one as unanswered for a wee bit to make sure the issue doesn't reappear.
    · Share on Twitter
  • Kendra_LittleKendra_Little Posts: 139 Gold 3
    Hi Peter,

    Thanks for reporting this.

    I've seen this issue before, and I was able to resolve it by manually deleting the shadow database (with the option to close existing connections when I do so). That is a workaround and not something we want users to have to do regularly, so if this issue persists after yesterday's release, we should look into it. I'll keep an eye out for it as well.

    Kendra
    · Share on Twitter
  • Ivo_MillerIvo_Miller Posts: 31 Silver 3
    This issue should be fixed as of version 4.2.20161, released yesterday.
    Ivo Miller
    RedGate Software Developer
    · Share on Twitter
Sign In or Register to comment.