Comments
Sort by recent activity
@Sergio R I am having issues with the internal objects in the database. That said this database has over 9k user objects as well so things are a bit sluggish. Build process locally with PowerShell take over 10 minutes to complete. Its a database schema with lots of legacy objects left around referencing objects that have changed so I expect breaks. I just wish this tool would allow me to flush them all out at once. I think the messaging could greatly be improved for cases where a build fails. It would beat having to run an extended event to catch failures to find more detailed information about the failures during the build. The invalid database object message is a false positive. SET NOEXEC ON explains why I am seeing that even though I wish I could pass a flag in PowerShell to disable that. @David Atkinson Thank you for the tip. SQL Prompt invalid objects times out. I will look at the SQL cop test. Thank you so much for providing those. Update: Third time was a charm for SQL Prompt Invalid Object search. I was able to get my list I needed. / comments
@Sergio R I am having issues with the internal objects in the database. That said this database has over 9k user objects as well so things are a bit sluggish. Build process locally with PowerShell ...
Hi Sergio, Its SQL Source Control and not SCA. @ERROR <> 0 SET NOEXEC ON" is issued for the start of any batch statement generated by Invoke-BuildDatabase. When an error occurs, all additional statements are compiled instead of executed. This is why I was seeing that the table didn't exist even though a create table. Is it possible, to have this disabled with a parameter at run-time so we could then flush out all the build errors in a build instead of just only getting the first error? I believe this forces every other call that depends on an object to say that the object is invalid because the build just compiles instead of executing the build scripts. Regards, John / comments
Hi Sergio,Its SQL Source Control and not SCA. @ERROR <> 0 SET NOEXEC ON" is issued for the start of any batch statement generated by Invoke-BuildDatabase. When an error occurs, all additional stat...
Thank you, Sergio. I will double check and make sure I am using x64 / comments
Thank you, Sergio. I will double check and make sure I am using x64
Thank you, Chris and Mac. I think I am getting hung up on the Pipeline for deployment and also the agent required for pulling and deploying locally. / comments
Thank you, Chris and Mac. I think I am getting hung up on the Pipeline for deployment and also the agent required for pulling and deploying locally.