Comments
Sort by recent activity
Yes, that's correct -- the "offline" method is the approach designed for scenarios where you want the static data to appear different in the target rather than what is in version control in some way. Thanks for the additional detail on your use case. Another question -- if you had a rules engine that would allow you to alert on this type of mistake -- either at the point where the user is working, or during a build process (or perhaps both), would that be sufficient? / comments
Yes, that's correct -- the "offline" method is the approach designed for scenarios where you want the static data to appear different in the target rather than what is in version control in some wa...
Hi @HorstKlein , Currently with the SQL Source Control object history feature you can either:
View the history of an existing object
View the history of the database by commit message
You can find the history of a deleted database object via the second option, but it may be somewhat cumbersome/ tedious to find. I explain this to say that there is a solution for this, but it will generally only be efficient if you are looking for something that happened in a recent commit OR if commit messages can be relied on to indicate when drops occurred. I've searched our User Voice forum and I don't see that we've had this as a feature request before from folks. If you wouldn't mind creating an item there, it would help us to track the request. If you can describe how often you use the object history feature and if you have any policies/process/change requirements around dropping or renaming objects, that would also be really useful for us. Kendra / comments
Hi @HorstKlein , Currently with the SQL Source Control object history feature you can either:
View the history of an existing object
View the history of the database by commit message
You can find ...
Hi @michaelmm , Thanks for reporting this. I see why it seems like the history feature would solve this in SQL Source Control, but it doesn't. This is very helpful feedback for us in thinking through user stories for viewing version control history. I am not sure if you are using this in an automation context, but one other scenario we are currently working on is more flexible alerting of commands like DROP, TRUNCATE, RENAME in automation contexts-- say to possibly warn or fail on a build when these keywords are present. (I don't mean that would negate the value of viewing history to find when something was dropped or renamed, but it seems like a complimentary feature and both would be desirable.) Cheers, Kendra / comments
Hi @michaelmm ,Thanks for reporting this. I see why it seems like the history feature would solve this in SQL Source Control, but it doesn't. This is very helpful feedback for us in thinking throug...
Hi @rknight , Thanks for chiming in. We don't presently have this on the roadmap for SQL Source Control. I would be very curious to know:
Are you already an Azure Data Studio User? If so, how much do you use it vs SSMS approximately?
If SQL Source Control had a fast performing standalone tool that could work in tandem with either GUI, would this be of interest to you?
If SQL Source Control offered the ability to be used via the command line in some ways, would that be of interest to you?
Thanks in advance, Kendra / comments
Hi @rknight ,Thanks for chiming in. We don't presently have this on the roadmap for SQL Source Control. I would be very curious to know:
Are you already an Azure Data Studio User? If so, how much ...
Hi @mirving , Presently the experimental method you're referencing in the article is the only way to use SQL Source Control in Azure Data Studio. Thank you very much for the feedback on it, it's incredibly useful for us to hear that. I am interested in learning more about how you use feature branches in general, if you don't mind sharing:
Are there times when you want to make a change in the database and commit this into more than one feature branch? If so, how do you currently go about this?
If I run through a scenario like you're describing -- add a table in my database and commit to BranchA, then switch to BranchB, SQL Source control will list the table in the 'Get latest' tab and essentially suggest 'undoing' the change in the database. Do you tend to use that?
Do you have other comments or feedback about your biggest pains or wishes for working with branches?
Cheers, Kendra / comments
Hi @mirving ,Presently the experimental method you're referencing in the article is the only way to use SQL Source Control in Azure Data Studio. Thank you very much for the feedback on it, it's in...
Hello, Thank you for confirming. With SQL Source Control, I believe that the setting you are looking for is called "Ignore users' permissions and role memberships". You set this on the "Setup" tab under "Comparison Options." You may also find some additional information useful in this article on Source Controlling Your Database Permissions, which is specific to SQL Source Control. Hope this helps, Kendra / comments
Hello,Thank you for confirming. With SQL Source Control, I believe that the setting you are looking for is called "Ignore users' permissions and role memberships". You set this on the "Setup" tab u...
Hi there, To clarify your setup, which tool are you using to commit changes to your project? Are you using SQL Source Control to do this? Or SQL Change Automation? Thanks, Kendra / comments
Hi there,To clarify your setup, which tool are you using to commit changes to your project? Are you using SQL Source Control to do this? Or SQL Change Automation?Thanks,Kendra
Hi @Koenraad.Dendievel, Thanks for letting us know about your use case. This enhancement is up for consideration and I've updated the request with the use case info you provided. It's just up for consideration and not something we're actively working on presently, but understanding customer impact definitely helps us. Kendra / comments
Hi @Koenraad.Dendievel,Thanks for letting us know about your use case. This enhancement is up for consideration and I've updated the request with the use case info you provided. It's just up for co...
And I've just found that I can answer this more fully before knowing which "authoring" tool you are using. There is a way that you can skip the build process if desired, by using the New-DatabaseProjectObject powershell cmdlet. Some notes on this:
You would implement this using a PowerShell step in Azure DevOps, instead of the graphic plugin. The documentation page linked above has examples for doing this (one example is for a SQL Source Control project, one is for a SQL Change Automation project)
The build process adds some additional value in terms of validation. It also creates a snapshot of the desired target schema which is used for things in the "Create Release Artifact" process, such as the changes report and the drift report. That means that if you skip the build process, you'll still have the ability to deploy, but won't have these extra features.
As mentioned above, this also skips the validation process.
I think that what you are mentioning above is that you might have more than one kind of build pipeline, and only run the "full" build when you are generating a NUGET package that is planned to be deployed to production? I'm not entirely sure what your branching strategy and development database workflow is, but combining the two approaches might work, and then you would still get the changes report, the drift report, etc for your production release artifacts. Cheers, Kendra / comments
And I've just found that I can answer this more fully before knowing which "authoring" tool you are using.There is a way that you can skip the build process if desired, by using the New-DatabasePro...
Hello, Sorry for the slow response, and thanks for the information that build time sounds like it is a pain point. Can I ask if you are using SQL Change Automation to deploy a SQL Source Control project, or is it a SQL Change Automation project that you are deploying with SQL Change Automation? Thanks, Kendra / comments
Hello,Sorry for the slow response, and thanks for the information that build time sounds like it is a pain point.Can I ask if you are using SQL Change Automation to deploy a SQL Source Control proj...