Comments
Sort by recent activity
Must have been a "ghost in the system". I restarted things, deleted the manually added files and tables, then just ran my table script in SSMS and this time the changes were picked up.
Very odd for a while there. / comments
Must have been a "ghost in the system". I restarted things, deleted the manually added files and tables, then just ran my table script in SSMS and this time the changes were picked up.
Very odd for...
At least we are in agreement - very strange indeed.
No sure what code you want. I have added two table definitions (each in a separate SQL file in the DB's repository folder). The tables now exist in the DB, but do not show in the "commit" panel.
The only change seen is a single test column I added to an existing table. / comments
At least we are in agreement - very strange indeed.
No sure what code you want. I have added two table definitions (each in a separate SQL file in the DB's repository folder). The tables now exist ...
As I said, column changes to existing table(s) are picked up fine.
I initially added new tables via SSMS. No changes detected to commit.
So, I added the SQL statements/files to the files in the DB repository folder. Still not picked up.
All that is being detected right now are user/role changes - which I didn't actually make.
Interestingly, SQL Compare, when run against my local DB and the running instance of the remote DB detects the tables that I have added (since, of course, they haven't been committed to source control yet and deployed). / comments
As I said, column changes to existing table(s) are picked up fine.
I initially added new tables via SSMS. No changes detected to commit.
So, I added the SQL statements/files to the files in the DB ...