Error: "A development source must be set to generate migrations."
87maxima
Posts: 7 New member
I am setting up a new SQL Change Automation job using SQL Source Control as the development source within SSMS. After going through the "new project" windows, a project appears to be successfully created, but the initial view of the project throws error "A development source must be set to generate migrations. <link>Set development source...</link>". Pressing on that link shows the SQL Source Control project is set as development source.
Any idea how to get SCA to acknowledge the source? The source control project functions correctly, all scripts look right within it.
Any idea how to get SCA to acknowledge the source? The source control project functions correctly, all scripts look right within it.
Answers
The workaround in the existing release is to manually set the shadow database in the user file. e.g.<ShadowConnectionString>Data Source=(localdb)\ProjectsV13;Initial Catalog=MyShadowDatabase;Integrated Security=True</ShadowConnectionString>
RedGate Software Developer
According to the SSMS interface I am on a version later than that: 4.2.20057.15888 did the error get reintroduced in this version? I don't see a user file being generated when using the SSMS interface, where would I find the file to try the work around?
We have just released again, version 4.2.20058.15937, and the issue should now be fixed.
Apologies again.
RedGate Software Developer