Comments
Sort by recent activity
I am also having a problem with SQL Compare detecting there is a scripts folder, unless launched from within SSMS using an actual database as the source (then changing it to source code).
Using SVN as repository and opening SQL Compare directly I haven't been able to detect the scripts folder. On migration wizard, migration scripts step is grayed out.
Steps to reproduce:
1. Have a database under source control, and at least one migration script checked into source control.
2. Open SQL Compare. (my version 10.2.0.1337)
3. Choose Source control as source.
4. Choose <Browse source control> in repository drop down.
5. Choose SVN
6. Paste or browse for Database Repository URL
7. Paste or browse for Migration Scripts Repository URL
8. Press [Link]
9. Select target database
10. Press Compare.
Expected result: Migration script symbol next to objects for which migration scripts were created. Step in wizard to select migration scripts to utilize.
Actual result: No migration script symbol for objects for which migration scripts were written. No step in wizard to select migration scripts to apply.
This behavior is different than if starting from SSMS, selecting a database to compare from initially, then switching to source control as the source.
In that case the symbol appears and the wizard step exists. / comments
I am also having a problem with SQL Compare detecting there is a scripts folder, unless launched from within SSMS using an actual database as the source (then changing it to source code).
Using SVN...