Comments
Sort by recent activity
Good to hear. Hope that continues to work for you. / comments
Good to hear. Hope that continues to work for you.
I'm not sure you can do this. Perhaps the best way to try this (not sure if this works and can't test right now), is to create a synonym and use that? It might resolve the reference, but I'm sure you don't necessarily want that to be the object deployed to production. Unfortunately, part of the issue is that we want to ensure that the dependencies are evaluated, which means that if you filter out the table, we still see a view dependency. Since we use SQL Compare, this limits some of the choices. There is an /EXCLUDE switch that might work, but is there a reason you don't want to source control the tables? If they aren't changed by you, there's no issue as there won't be changes deployed. / comments
I'm not sure you can do this. Perhaps the best way to try this (not sure if this works and can't test right now), is to create a synonym and use that? It might resolve the reference, but I'm sure y...
Can you post some of the log? Are you using the cmdlet to create the release db, or just point to the target and generate an upgrade script? / comments
Can you post some of the log? Are you using the cmdlet to create the release db, or just point to the target and generate an upgrade script?
The build process always builds a new database. That's the point of build, to verify all the SQL works without issues. The release step is what does the upgrade step. Make sure your target is set to an Azure database, otherwise there are sometimes items included from the on-premises SQL Server perspective that cause issues in Azure SQL DB. / comments
The build process always builds a new database. That's the point of build, to verify all the SQL works without issues. The release step is what does the upgrade step. Make sure your target is set t...
Under teh CASE section, you have the "collapse" checkbox set to 80. This is less than 80 characters, so it's one line, which I assume you want. When I copy/paste this, I get the alignment correctly with your style could there be some strange characters added in your query? If you copy paste in notepad and then paste back? [image] / comments
Under teh CASE section, you have the "collapse" checkbox set to 80. This is less than 80 characters, so it's one line, which I assume you want. When I copy/paste this, I get the alignment correctly...
A couple things, first, rather than try to decode your PoSh, can you explain what and where you're trying to do something? We can't see your environment, so I have no idea where dev, test, production are or what the machines are. Second, there is no issue with a database developed in any way. The first time you start using SCA to deploy, it will square things up. Third, are you using SCA in VS as the client or SQL Source Control in SSMS for development? SCA biuld/release is the same, but it helps to guide you to know. Next, the purpose of build is to validate your SQL. the purpose of seeing a target is to ensure we build a valid package. If you can't see production, you will have issues here, especially with drift. Drift isn't an issue overall, but you want to account for it, and so any issues need to be fed back to development (recommended) to clear the drift issues. If you use the SkipDriftCheck (?) flag, then you risk the package not deploying, which defeats the purpose of using a DevOps style flow for development. If you can't connect to production, what I'd recommend is that you get a SQL Compare snapshot of prod and pull that back, load that to a staging database and use that as the target. You don't need data (really), just schema. Of course, data changes in your release aren't tested, but this is a lightweight way of getting schema deploys out. You can schedule this, make it part of the pipeline, or something else, but you need a good view of production schema to do the release packaging. If that doesn't make sense, you have other questions, or I've misrepresented what you're doing, please let me know. / comments
A couple things, first, rather than try to decode your PoSh, can you explain what and where you're trying to do something? We can't see your environment, so I have no idea where dev, test, producti...
A couple things I heard back. First, did you have a new Posh session between the provider install and the get install? This page (https://documentation.red-gate.com/sca3/getting-started/installation/installing-powershell-components) asks for that. Also, is the new session elevated? / comments
A couple things I heard back. First, did you have a new Posh session between the provider install and the get install?This page (https://documentation.red-gate.com/sca3/getting-started/installation...
hmm, I've asked a few people for help here. I'm not sure what's broken. / comments
hmm, I've asked a few people for help here. I'm not sure what's broken.
Try a -Force here. I think that will help, but not in a place to test, and everyone in the UK is gone for the weekend. Can you check the version of SCA on your build server? / comments
Try a -Force here. I think that will help, but not in a place to test, and everyone in the UK is gone for the weekend. Can you check the version of SCA on your build server?
There is a need to create and destroy databases for sure. The "Build" actually wants to run the pre, which does contain a create db, and run all the code to ensure it compiles correctly, as that's the only SQL Server compiler we have. In terms of using a test instance, we usually go with SA, but I suspect that you could get by with: dbcreator, which hopefully would give you db_owner in the build db and the shadow db. For the release part, you need rights to read the target db. Note that builds are not usually to a specific name, unless you are sure there aren't collisions with other developers. Since we may want concurrent builds from checkins at similar times, the build task will generate a random name. / comments
There is a need to create and destroy databases for sure. The "Build" actually wants to run the pre, which does contain a create db, and run all the code to ensure it compiles correctly, as that's ...