User profile for way0utwest

The Output window (lower pane by default), is the one to use. There's a drop down in there, and you typically want the Build or General items selected, depending on what you're doing. A deploy usually results in a build, so be sure to check that. VS usually switches this for you,but if you have it set to your VCS or something else, you might not notice. / comments

The Output window (lower pane by default), is the one to use. There's a drop down in there, and you typically want the Build or General items selected, depending on what you're doing. A deploy usua...

0 votes

I think gitflow is unnecessarily complex, and it's problematic for databases, but if you use it, that's OK. If you look at gitflow, you aren't putting your changes from the local machine to the remote db, are you? You are sending your changes to the VCS and the SCA automation process should push them to another machine. However, that doesn't matter. You push/pull your changes from VCS, which is what other developers do. First, you need strong communication if developers might touch the same object. That can be something like a Slack channel, or some other mechanism for a developer to just say "I've changed x". This important, otherwise you'll end up with hard merges. You could even make a quick "I'm doing this" in your standup. Your gitflow should have feature branches, correct? This means you have master---------o---o---------------------o dev --------0/----o/---------o--------o fb1 \---o---\-o----/ fb2 \----o/ In this case, master is at the top, where I release. Dev is below. Let's have Steve work fb1 and Andy work fb2. Andy gets dev copied and then commits. He is happy with his commit (o) and pushes up to dev. This is the second o. This gets merged to master. Steve later gets a branch from dev, fb1, and works and commits. Change is good. He then pulls from dev, which at this point, should include the change from Andy. Steve needs to merge this in his branch, which might be simple, might be hard. If there is communication, either there is no conflict or there is the need to resolve changes. Steve then commits again and pushes/merges changes to dev later. The key here is that you need to have short lived branches for the db, since this is a shared area. If you need to work, make your branch and push changes that you know work, immediately. If you're not sure or this takes time, then stage changes and pull from dev again to get anything merged in. Then try applying your changes again. The really issue here is that the longer branches live, the more likely there are conflicts. Imagine that you have multiple C#/Java developers working on the same method. If they each make a quick change and merge, the other likely gets the changes. If they wait weeks, merging might be really hard. The same thing with databases. What I'd suggest if that you plan out changes, maybe get an idea, and save them after you've experimented a bit. This might be an hour or a week. Then rebuild the db branch again, essentially a new feature branch, and make your changes. If they're good, immediately commit and merge back to dev. / comments

I think gitflow is unnecessarily complex, and it's problematic for databases, but if you use it, that's OK.If you look at gitflow, you aren't putting your changes from the local machine to the remo...

0 votes

No. You should never make changes in Test that are needed. This defeats the purpose of using a pipeline, and is a source of problems. What you should always do is release change A to your VCS. Then this is either built or reviewed and using an automated, consistent process, release to test. If you find an issue, then reproduce that in dev, or if you can't, try the fix in test and undo it. Then go back to Dev and make the change (Change [image] , upload and re-release. This is one reason your release to test ought to reset your schema to what is production like. If you're using SCA, only the new change from dev (Change [image] will be released. Then you can test ,and when you release to downstream environments (Staging, prod, acceptance, etc.), both Change A and Change B will be in the package. This is similar to what Microsoft does with SQL Server. If they find a bug, they fix in SQL 2017 branch. However, they have to manually backport this to SQL 2016, which is often taking the changes and adding them to the other environment. / comments

No. You should never make changes in Test that are needed. This defeats the purpose of using a pipeline, and is a source of problems. What you should always do is release change A to your VCS. Then...

0 votes

Where are you excluding users? Is this a filter in SCA/SQL Source Control? Or are you adding the switch to the DLM cmdlets to ignore users and roles? / comments

Where are you excluding users? Is this a filter in SCA/SQL Source Control? Or are you adding the switch to the DLM cmdlets to ignore users and roles?

0 votes

You all your developers using the same Azure SQL Database? Just curious. In terms of fixing the same project, yes, set a local source (Local SQL instance, Express, or LocalDB) and then make that the default. Then you can change the main connection. We are doing some work here that I hope will make this easier to change independently. / comments

You all your developers using the same Azure SQL Database? Just curious.In terms of fixing the same project, yes, set a local source (Local SQL instance, Express, or LocalDB) and then make that the...

0 votes

You should be able to. I haven't tried it, but the steps for configuring the shadow are here: https://documentation.red-gate.com/sca3/developing-databases-using-sql-change-automation/validating-change-scripts/target-and-shadow-databases / comments

You should be able to. I haven't tried it, but the steps for configuring the shadow are here: https://documentation.red-gate.com/sca3/developing-databases-using-sql-change-automation/validating-cha...

0 votes

I have 9.2.7, and with my format, or the AB style Alex added, this formats. With Mathew's file above, this doesn't. Mathew, I think this is something with the various setting combinations you've chosen. As I mentioned above, if you play with the Control Flow, this seems to adjust things. I think the "Collapse" checkbox in this section causes issues with various other settings. Can you remove this? / comments

I have 9.2.7, and with my format, or the AB style Alex added, this formats. With Mathew's file above, this doesn't.Mathew, I think this is something with the various setting combinations you've cho...

0 votes

This is strange. I've reported as a possible bug, but it's a bank holiday in the UK today. The thing I notice with your setup, if I change the Wrap after setting in Control Flow to a lower value, like 70-80, I get better behavior. I'm not sure of the interaction here, but I'll try to find an answer. / comments

This is strange. I've reported as a possible bug, but it's a bank holiday in the UK today. The thing I notice with your setup, if I change the Wrap after setting in Control Flow to a lower value, l...

0 votes

OK, I have these answers: ========= This is due to the Control Flow options they have set and the example they use in the different cases. So they have "Place BEGIN keyword on new line" true "Indent BEGIN END keywords" false "Indent contents of statements" true "Collapse statements shorter than <100> characters" true In the first example ```IF @Country = 'USA' BEGIN SET @FormatCode = 1; END; ELSE BEGIN SET @FormatCode = 2; END;``` It's collapsing the statements because they are shorter than 100 characters - this overrides the Begin on new line and the indent contents of statements. It does something odd though if you make "Place BEGIN keyword on new line" false but leave the others - it then indents the second SET statement which I think is probably a bug. In their last example the content of the BEGIN/END is more than 100 chars and so it doesn't collapse it. This is all independent of how far the IF is indented as that will be set to the correct indention if the collapse is not set. So if you add another BEGIN / END around the above query and turn off collapse, it will indent the content of the overall BEGIN as well as the internal BEGINs to the correct place ======== I've played with the style. I think the removing the collapse item fixes most of this, but the SETs are still wrong if things are not included inside some other structure. Is this just a script you have or is it part of a larger set of work? / comments

OK, I have these answers:=========This is due to the Control Flow options they have set and the example they use in the different cases. So they have"Place BEGIN keyword on new line" true"Indent B...

0 votes

Hmm, with your style, I get this: IF @Country = 'USA' BEGIN SET @FormatCode = 1; END; ELSE BEGIN SET @FormatCode = 2; END;Not sure why you get the weird formatting. I'll have to bump this. / comments

Hmm, with your style, I get this: IF @Country = 'USA' BEGIN SET @FormatCode = 1; END; ELSE BEGIN SET @FormatCode = 2; END;Not sure why you get the weird formatting. I'll have to bump...

0 votes

How can we help you today?

way0utwest

Comments