SCA in SSMS add-in mostly "(Not Responding)"

PeterDanielsCRB · January 23, 2020 6:14PM

My first attempt at using SCA SSMA add-in is not going very smoothly. (I have used SCA in VS for a couple of years). I have the latest SSMS 18.4 and the latest SQL toolbelt (DL'd and installed today). Admittedly, the DB I'm working with has 871 tables and 6572 sprocs, so I expect some slowness - just not 10-20 minutes of grey-screen "(Not Responding)". Wondering if I should give up on the SSMS and return to the comfort of VS SCA? Or are there tips for helping this along? Note that I was in the process of attempting to apply the baseline to my local dev sandbox shell DB.

TIA,

-Peter

Sergio R · February 21, 2020 4:03PM

The issue initially reported SCA in SSMS add-in mostly "(Not Responding)" has now been fixed, please upgrade to version 4.2.20036 or later

Sergio R · January 24, 2020 2:42PM

Hi Peter,

I am sorry that you are having issues with SCA for SSMS.
I will follow up using our support system since we need additional diagnostic data to troubleshoot your issue.

Kind Regards,

PeterDanielsCRB · January 24, 2020 4:34PM

Much appreciated, @Sergio R . I will want to strategize with the support team on how best to handle some other issues with baselining this DB. It has programmable objects that have linked server refs, cross DB refs, etc. Getting a deploy to my dev DB has been a challenge.

Sergio R · January 24, 2020 5:11PM

We will look at the logs and will get back to you soon.

Regarding cross-database dependencies the following article might help:
https://www.red-gate.com/hub/product-learning/sql-change-automation/resolving-cross-database-dependencies-in-sql-change-automation-using-local-databases-or-clones

PeterDanielsCRB · January 24, 2020 5:24PM

That article is helpful - thanks. I want to explore the idea of a pre-deploy script making stubs. I'm still a bit confused on how to best ignore certain objects and programmable object scripts without having to redo the entire baseline generation that takes so long. I do realize I'm hacking away in SCA at this point. Just want to get this puppy into source so I can develop some new objects.

David Atkinson · January 24, 2020 5:31PM

@PeterDanielsCRB - Is there a reason why you can't have copies of the dependent databases in your environment so the baseline script runs?

PeterDanielsCRB · January 24, 2020 5:35PM

Thanks, @David Atkinson. I've been working that angle, too. It worked for one simple DB; I just created a shell for it. The other DBs have the same kind of problems - cross refs, and are too large to restore onto my laptop. Considering a cloning tech like SQL Clone/PSDatabaseClone.

David Atkinson · January 24, 2020 8:49PM

@PeterDanielsCRB - You mean a shell which is schema object only (no data)? If so, that's an interesting idea. SQL Clone should allow you to not only spin up dependent databases in dev, but also throughout your CI/CD pipeline.

PeterDanielsCRB · February 24, 2020 8:48PM

I hear ya, @David Atkinson - re: full clones. Just not sure we have the $ for SQL Clone/Provision at this time. Ergo, looking into PSDatabaseClone. Meanwhile, I'm going to mark @Sergio R 's last one as the answer even though I have not tested it again since the fix. I have confidence in the team.

SCA in SSMS add-in mostly "(Not Responding)"

Best Answer

Answers

Product Learning

Community Forums

Events & Friends

Simple Talk