Comments
Sort by recent activity
David Atkinson wrote:
We don't have this integrated into SSMS right now so the process in the meantime is:
1) Using Tortoise (for example) get the old tag/revision of the schema scripts folder to a temporary folder.
2) Load this as the source database in SQL Compare Pro as a scripts folder, and load your dev environment as the target.
3) Run the comparison and synchronization as you would normally do in SQL Compare.
Please let me know if this isn't straightforward.
Regards,
David Atkinson
Red Gate Software
I'm trying to do the same thing with TFS. Can you confirm what I'm doing would be the correct procedure. First, I've created the link to TFS:
1) In Visual Studio, I've created a folder for the DB as $/ProjectA/Databases/TestDatabase
2) I've linked my TestDatabase in SQL Management Studio to this path and commited changes.
Back in Visual Studio, on the folder $/ProjectA/Databases\TestDatabase, I apply a label "Initial Commit".
Now, lets say down the road, after several changes and updates to the database, I want to get the inital database, I think this would be the procedure:
1) In Visual Studio, on the folder $/ProjectA/Databases\TestDatabase I get a specific version based on the label "Initial Commit".
2) Then in SQL Compare 8, I set the source to "Scripts Folder" and Target to "Database".
3)I specify my local path C:\ProjectA\Databases\TestDatabase as the scripts folder and the target to my server and the database I want to restore as.
4) Click "copy"
Is this correct?
Thanks,
Brandon / comments
David Atkinson wrote:
We don't have this integrated into SSMS right now so the process in the meantime is:
1) Using Tortoise (for example) get the old tag/revision of the schema scripts folder t...