Comments
Sort by recent activity
Perfect, thanks [image] / comments
Perfect, thanks
Hi Mike,
thanks for your reply. Ok, that seems to be the best option. We'll investigate the possibility of deleting the migration scripts after we included them in our setup as well, but I think removing them from our workflow and use SQL Compare for the scripts is the way to go here. / comments
Hi Mike,
thanks for your reply. Ok, that seems to be the best option. We'll investigate the possibility of deleting the migration scripts after we included them in our setup as well, but I think re...
Hi Alex,
thanks for you reply. We'll look into that. Indeed it seems to be a better fit to our use case. But with SQL Source Control we had full integration in SSMS. Looks like with ReadyRoll we need to create a Visual Studio solution to handle creating scripts and commiting them to our TFS, right? This could eventually be a problem with some of our developers who are working only in SSMS right now...
Also, is ReadyRoll only available as part of the SQL Toolbelt or can we license it seperately as a stand alone product?
Thanks again.
Matthias / comments
Hi Alex,
thanks for you reply. We'll look into that. Indeed it seems to be a better fit to our use case. But with SQL Source Control we had full integration in SSMS. Looks like with ReadyRoll we ne...
Also, is there a way to, kind of, clean up all existing migration scripts, e.g. removing them from the existing scripts view but leaving the objects history intact?? / comments
Also, is there a way to, kind of, clean up all existing migration scripts, e.g. removing them from the existing scripts view but leaving the objects history intact??