Comments
Sort by recent activity
Thanks for sharing your experience cjoneslib. We abandoned our POC of this product in Q1. Reverted back to SQL Source Control for all database repos. I've been stalking the release notes every month to see if the product changes to address our issues. Our team would really like to use it due to all of the other benefits. However, this issue is a blocking obstacle for us. / comments
Thanks for sharing your experience cjoneslib. We abandoned our POC of this product in Q1. Reverted back to SQL Source Control for all database repos. I've been stalking the release notes every m...
Thanks Kendra & Pete. The combo of your responses illustrates how we can effectively deal with the scenario. Going forward do you recommend the SCA/migrations approach or the SOC/state approach when multiple developers (3-6) are actively working in the database project? Note: We've been using the SOC/state approach for 2-years, and we are currently evaluating SCA/migrations on a greenfield project. Kicking the tires so to speak before converting. / comments
Thanks Kendra & Pete. The combo of your responses illustrates how we can effectively deal with the scenario. Going forward do you recommend the SCA/migrations approach or the SOC/state approach w...
@Kendra_Little Were the developers able to address my question? / comments
@Kendra_Little Were the developers able to address my question?
My filter and compare options are attached for reference. I am building in Microsoft Visual Studio Team Foundation ServerVersion 15.117.27414.0 Running SQL Change Automation:Build v3.1. / comments
My filter and compare options are attached for reference. I am building in Microsoft Visual Studio Team Foundation ServerVersion 15.117.27414.0Running SQL Change Automation:Build v3.1.
Hello Kendra, I executed your SQL in my environment and it failed with the following message: 2019-02-07T15:59:14.4268592Z ##[warning]The error 'The object 'dbo.duplicate' does not exist or is invalid for this operation.' occurred when executing the following SQL: 2019-02-07T15:59:14.4268592Z ##[warning]CREATE TRIGGER [dbo].[tr_duplicate] ON [dbo].[duplicate] AFTER INSERT AS 2019-02-07T15:59:14.4268592Z ##[warning]BEGIN 2019-02-07T15:59:14.4268592Z ##[warning]DELETE FROM dbo.duplicate WHERE 1 = 0 2019-02-07T15:59:14.4268592Z ##[warning]END / comments
Hello Kendra,I executed your SQL in my environment and it failed with the following message:2019-02-07T15:59:14.4268592Z ##[warning]The error 'The object 'dbo.duplicate' does not exist or is invali...
We invoked the desired behavior for scenario #3 by changing this option to false: <IgnoreDatabaseAndServerName>False</IgnoreDatabaseAndServerName> Can you confirm if this is valid/safe? / comments
We invoked the desired behavior for scenario #3 by changing this option to false:<IgnoreDatabaseAndServerName>False</IgnoreDatabaseAndServerName>Can you confirm if this is valid/safe?
I don't believe this is the case. The synonym section of my filter.scpf is: <Synonym version="1"> <Include>True</Include> <Expression>TRUE</Expression> </Synonym> My ComparisonOptions.xml file contains this entry: <IgnoreSynonymDependencies>False</IgnoreSynonymDependencies>
/ comments
I don't believe this is the case.The synonym section of my filter.scpf is: <Synonym version="1"> <Include>True</Include> <Expression>TRUE</Expression> </Synonym>My Compariso...
Alex, I see that now. Thanks for the resolution. / comments
Alex, I see that now. Thanks for the resolution.
Alex B >> Partition functions & schemes are not filtered out in my SQL Compare session. The functions & schemes do make it to source control. However, SQL Compare ignores differences between source control and a target database. As previously mentioned, I added a function to the database that didn't exist in the target. SQL Compare didn't detect the difference. Julia >> Thanks for identifying the root cause. / comments
Alex B >> Partition functions & schemes are not filtered out in my SQL Compare session. The functions & schemes do make it to source control. However, SQL Compare ignores differences between sour...
Alex, Thanks for the feedback regarding rowversion & timestamp. We are in the process of migration to SQL 2016. We plan to convert all timestamp columns to the rowversion type since MS deprecated timestamp. Regarding partitioning, I conducted a test by introducing a partition function in the target database that didn't exist in source control. SOC didn't detect the drift from SOC. / comments
Alex,Thanks for the feedback regarding rowversion & timestamp. We are in the process of migration to SQL 2016. We plan to convert all timestamp columns to the rowversion type since MS deprecated ...