User profile for way0utwest

What's the build target? The only compiler the build process has is the SQL Server engine. If you've targeted LocalDB or a version that doesn't support TRIM(), then things might not work. / comments

What's the build target? The only compiler the build process has is the SQL Server engine. If you've targeted LocalDB or a version that doesn't support TRIM(), then things might not work.

0 votes

The developers are aware this is an issue and they're looking into it. No word on when this might be fixed, but I'm hoping soon. / comments

The developers are aware this is an issue and they're looking into it. No word on when this might be fixed, but I'm hoping soon.

0 votes

Is there broken code after the area you're trying to format? If I get my code into a batch, it seems to format. If you have an example of the code for me to test, I'd be happy to. I have 9.2.7 on this machine, but 9.2.9 on another. / comments

Is there broken code after the area you're trying to format? If I get my code into a batch, it seems to format. If you have an example of the code for me to test, I'd be happy to. I have 9.2.7 on t...

0 votes

I've noticed this as well. I've sent a note off to see if this is a fundamental behavior change or a bug. I have been able to get this to work by putting a "GO" before my statement/query and then formatting it. / comments

I've noticed this as well. I've sent a note off to see if this is a fundamental behavior change or a bug. I have been able to get this to work by putting a "GO" before my statement/query and then f...

0 votes

Sorry, this process sometimes is a bit of a chicken and egg, going around in circles when trying to explain the process. In case someone else is following, here's what I recommend. Let's say I have a procedure that I wanted created called dbo.SetDateforClass. This looks like this in my programmable object: CREATE OR ALTER dbo.SetDateforClass<br>  @ClassID int<br>, @dt date<br>as <br>begin<br>update Class<br> set StartDate = @DTs <br>where ClassId = @ClassID<br>end I add this to my database and then add a migration script that looks like this. <br>exec dbo.SetDateforClass 1, getdate()<br>exec dbo.SetDateforClass 2, getdate() Now, when I refresh the project, this compares to the shadow database. The migration scripts execute first, then the programmable objects. In this case, I'll get an error as the proc doesn't exist in Shadow yet, so the script fails. This worked in the main development database since the chronology was correct in how I built the objects. To fix this, I recommend this: change the migration script to: <br>if not exists( select name from sys.objects where name = 'SetDateforClass')<br>  begin<br>CREATE OR ALTER dbo.SetDateforClass<br>  @ClassID int<br>, @dt date<br>as <br>begin<br>update Class<br> set StartDate = @DTs <br>where ClassId = @ClassID<br>end<br>goexec dbo.SetDateforClass 1, getdate()<br>exec dbo.SetDateforClass 2, getdate() This will deploy the procedure as part of the migration script and then execute it. Later, the programmable object will overwrite this procedure with the same definition and the compare with the Shadow db for validity, as well as a build or downstream deploy, will work. If the procedure gets updated with a new parameter or different logic, that will be deployed, but this migration won't run again. However, if a new developer sets up from scratch, when they load the project and pick databases, this migration script will work (likely no data, so no effect) and then the updated procedure definition will be deployed as a part of the programmable object deployment. / comments

Sorry, this process sometimes is a bit of a chicken and egg, going around in circles when trying to explain the process. In case someone else is following, here's what I recommend.Let's say I have ...

0 votes

I'm assuming your migration script uses the procedure to do some work? I'd that right? What is say here is you can really only do one thing and thats include the proc crrate in the migration script . It will also be in the programmable object and that should just ovewrite with the version stored there. I'd do this in an idempotent way so that in future deployments if the proc exists, we don't try to recreate it .Not create it alter but an if exists(check sysobjects). Toss isn't great but it does solve the issue here. In the future, this also ensures builds work from scratch . Even if the proc changes, the valid version of the proc that works with this migration script works. I think if you deoy the proc first, to both shadow sha downstream environments, then add the script this may work, but if have to test. However, any deployments to a new system, like a new developer setup, would fail so I'd rather just inline the proc in the migration script, knowing that all future changes are handled as a part of the programmable object / comments

I'm assuming your migration script uses the procedure to do some work? I'd that right?What is say here is you can really only do one thing and thats include the proc crrate in the migration script ...

0 votes

the order of when you do things sometimes becomes an issue. The idea with SOC is that it's always linked between your branch and the db. If you unlink, relink, you'll get into strange places. The goal here is to get changes from your VCS into the db first, since those can be made by other users, and then try to get your changes in there. In this case, I think you confused this by linking after doing work. The idea with a live database is that you are pulling to a blank VCS system, not using this to get changes to/from the VCS. That's a model that is fraught with issues. / comments

the order of when you do things sometimes becomes an issue. The idea with SOC is that it's always linked between your branch and the db. If you unlink, relink, you'll get into strange places. The g...

0 votes

With my style, I get this: <div>IF @CalculateHeld = 'Yes'</div><div>BEGIN</div><div>    SELECT *</div><div>    FROM [#HeldFunds]</div><div>    WHERE [HeldAmount] > 0;</div><div>    DROP TABLE [#HeldFunds];</div><div>END;</div><div>ELSE</div><div>BEGIN</div><div>    SELECT *</div><div>    FROM [#HeldFunds2]</div><div>    WHERE [HeldAmount] > 0;</div><div>    DROP TABLE [#HeldFunds2];</div><div>END;<br></div> What I'd suggest is look at the whitespace and the control flow sections. Watch out for checking the "wrap if longer than" items. I've had some strange behavior here when these are applied with certain values. / comments

With my style, I get this:<div>IF @CalculateHeld = 'Yes'</div><div>BEGIN</div><div>    SELECT *</div><div>    FROM [#HeldFunds]</div><div>    WHERE [HeldAmount] > 0;</...

0 votes

Honestly, what to do here is actually fix this as a part of build and fail the build if the constraint isn't named with doso standard. This for a couple things. Developers actively consider the constraint more and you also ensure no duplicate constraints get generated by using a standard That being said, it would be nice for SCA to generate these according to some pattern and offer to fix your dev db / comments

Honestly, what to do here is actually fix this as a part of build and fail the build if the constraint isn't named with doso standard. This for a couple things. Developers actively consider the con...

0 votes

There is no workaround here. The solution is to name your constraints. They should be consistently named in all environments to ensure you can alter/drop them easily. / comments

There is no workaround here. The solution is to name your constraints. They should be consistently named in all environments to ensure you can alter/drop them easily.

0 votes

How can we help you today?

way0utwest

Comments