Comments
Sort by recent activity
csmith wrote:
Hi
Can you please confirm what you mean by 'associated objects'?
In SQL Source Control version 3 we added Migration Scripts, which must be committed with associated objects. We also enforce changes to be committed together it they are Data and Schema changes related to the same object.
Would you be able to post some brief steps we can take to reproduce the issue?
Many thanks,
Chris
"We also enforce changes to be committed together if they are data and schema changes related to the same object". That is the part I want made optional. When I go to commit a change on a sproc say, I get a popup with numerous other objects already selected and a check box checked to commit all of those other objects I DID NOT SELECT. If I mistakenly just hit enter or continued without UNCHECKING the box I would commit those other objects I did NOT ASK TO BE COMMITTED. / comments
csmith wrote:
Hi
Can you please confirm what you mean by 'associated objects'?
In SQL Source Control version 3 we added Migration Scripts, which must be committed with associated objects. We als...
csmith wrote:
Hi
Just to explain why this behaviour has changed - we had a number of requests to stop ignoring FILLFACTOR and INDEXPADDING by default in the comparisons that SQL Source Control performs. Ignoring these changes is the default option for SQL Compare, but we thought it was a change that SQL Source Control users would generally want to see.
However, what we really want to do is allow the user to configure this setting (as they can in SQL Compare)....
Therefore, we are currently working on adding a comparison options configuration file to SQL Source Control that will allow the user to set FILLFACTOR to be ignored if they so wish.
We are hoping to release this in the next few weeks via our 'Check For Updates' mechanism. I will add a post to this thread when that build is available.
Best regards,
Chris
I to want to see some configuration options in the SSC compare. / comments
csmith wrote:
Hi
Just to explain why this behaviour has changed - we had a number of requests to stop ignoring FILLFACTOR and INDEXPADDING by default in the comparisons that SQL Source Control p...