Comments
Sort by recent activity
Thanks Christian, will take that under advisement. / comments
Thanks Christian, will take that under advisement.
Thanks for your reply, but it seems to contradict the page I linked. It clearly says "with the exception of" for SQL MI. Any other ideas? [image] / comments
Thanks for your reply, but it seems to contradict the page I linked. It clearly says "with the exception of" for SQL MI. Any other ideas?
Thanks, that would likely work as well, but I fixed it by appending the buildId to the nuget package name. / comments
Thanks, that would likely work as well, but I fixed it by appending the buildId to the nuget package name.
@DustinM Thanks for the reply, however it does not fully answer my question. I can filter out the entire schema of replicated tables when doing the compare, but any programmable objects that depend on replicated tables won't build in the event that the underlying tables are changed. I misspoke in my original post, as the replicated tables are in my baseline (started from an existing production database). So what I am wondering is the best way to have these objects in the schema model so that the build and release pipeline will work. From what I can tell my options are: 1. import the changes into the schema so the build works, but what happens when the release is deployed? Will it try to alter the replicated tables? (Note that they will already have been changed in the target) 2. Should I remove the replicated tables completely from my schema model and recreate them through scripts when building the project? Where would they go? In a Pre-Deployment sql file or some where else? Keeping in mind that I do not want them to be deployed, only there for the build to work. I know that they will be in my target DB when the deployment happens. Thanks in advance, Garth / comments
@DustinM Thanks for the reply, however it does not fully answer my question. I can filter out the entire schema of replicated tables when doing the compare, but any programmable objects that depen...
@Kendra_Little How would one go about disabling the validation in the SCA project? I am in the same situation but we are using SQL LocalDB on a self-hosted Agent. I have a synonym that points to another database that ultimately will be on the same server as the database being released. Thanks. / comments
@Kendra_Little How would one go about disabling the validation in the SCA project? I am in the same situation but we are using SQL LocalDB on a self-hosted Agent. I have a synonym that points to ...
@Nick_Foster Thanks, that's basically what we have wound up doing. A bit hacky in my opinion, but it gets the job done. / comments
@Nick_Foster Thanks, that's basically what we have wound up doing. A bit hacky in my opinion, but it gets the job done.
@Nick_Foster Did you ever find a reasonable solution for this when using Hosted Agent builds? I am in the same boat, and all I can find is for scripted solutions. Thanks. / comments
@Nick_Foster Did you ever find a reasonable solution for this when using Hosted Agent builds? I am in the same boat, and all I can find is for scripted solutions. Thanks.