Comments
Sort by recent activity
David Atkinson said:
@Sebazzz - If you use SQL Source
Control, and you intend to use the migrations
feature please DM or email me your serial key and we will ensure that SCA migrations is available to you. David Atkinson Product Manager Redgate David.Atkinson@red-gate.com
Hi David, We were never contacted. This is even more frustrating because on some databases we can't create any migrations at all. SQL Source Control keeps crashing - even when creating a blank script. / comments
David Atkinson said:
@Sebazzz - If you use SQL Source
Control, and you intend to use the migrations
feature please DM or email me your serial key and we will ensure that SCA migrations is ava...
My concern is that you now force customers on a SQL Toolbelt Essentials license to a much more expensive license (+$1500 per seat) license. Is that observation correct? / comments
My concern is that you now force customers on a SQL Toolbelt Essentials license to a much more expensive license (+$1500 per seat) license. Is that observation correct?
David Atkinson said:
We plan to publish more help on the differing approaches, outlining the pros and cons of each.
Do you have an update on this, David? Thank you. / comments
David Atkinson said:
We plan to publish more help on the differing approaches, outlining the pros and cons of each.
Do you have an update on this, David? Thank you.
David Atkinson said:
@TheoL - I have emailed you separately about this.
Can we keep this discussion public, please?
This also affects us. We have the toolbelt license, and I'm afraid this means our entire license for SQL Source Control useless for us as well. The backdoor method is only a temporary solution of course. / comments
David Atkinson said:
@TheoL - I have emailed you separately about this.
Can we keep this discussion public, please?
This also affects us. We have the toolbelt license, and I'm afraid this ...
David Atkinson said:
@Sebazzz - SQL Source Control is still very much supported. If you're using SQL Source Control the obvious option is to carry on using this and simply use SQL Change Automation to generate migrations scripts. Have you got any specific questions on this approach? (We would recommend against using the back door except as a temporary measure)
I'm unclear what the value of SQL Source Control is when we would have SQL Change Automation. Apparently from SQL Change Automation you primarily work from the project (apparently it is the SSDT equivalent from Redgate), but other than that you can use manual migrations and version the database. --
The problem is that we currently use the manual migration feature. Not only for data migrations, but for every migration. The resulting migration scripts we stitch together and hand over to MSDeploy, which deploys these changes to environments where no direct SQL connection from the build server is possible. These changes are also deployed together with data migrations from an internally developed tool that allows our clients to translate records in our database.
/ comments
David Atkinson said:
@Sebazzz - SQL Source Control is still very much supported. If you're using SQL Source Control the obvious option is to carry on using this and simply use SQL Change Auto...