Comments
4 comments
-
Sorry about that - I'll look through all the postings prior to listing another entry.
Thanks,
Roman -
Hi Roman,
No problem. I'm glad you were able to find this on our Suggestion Forum. We are currently working on the Revert functionality. If this is important to you, you can comment/vote at http://redgate.uservoice.com/forums/390 ... ?ref=title
Thank you! -
One more thing that I wanted to mention... In this example, you want to revert/undo a dropped table. In a future SQL Source Control version, you will be able to do this, but it will only bring back the table's schema and not the data that was in the table. Does that make sense?
SQL Source Control is not a replacement for database backups. After reverting the schema, you could use our SQL Data Compare to synchronize the data in that table from a recent backup or from another dev/test/production db. Since it's a development db, you may not be concerned about the data anyways.
In a future version of SQL Source Control, we are considering giving users the option to also source control data. This would be useful for static/reference/lookup data that is part of the application and not really recommended for transactional data. If this data was in source control, then this should be revertable as well. This is a ways out right now... -
It does makes sense. The drop table was probably a poor example of a goof.
Thanks!
Add comment
Please sign in to leave a comment.
Sorry if I missed this, but if I have a linked DB, create objects, checkin, so all objects are at version 1. Within SSMS, I drop table "keywords", so SubVersion has dbo.keywords.sql, but the DB does not.
Now I realize the error of my ways and want to revert the dropped table - how do I do this?
Thanks!
Roman