Comments
1 comment
-
Thanks for sending in the error report and posting this issue here.
I think you see an error like "Nothing to Commit" because the dbo schema shows up on the Commit list, but then it doesn't actually recognize this change so it thinks there is nothing to commit.
We are currently working this issue. Our internal reference number is SOC-799.
For now, please just ignore this on your commit list. If there are multiple objects to commit, it will NOT error because there will be something else to commit.
There is a manual workaround if you want to get this object off your commit list and you don't expect it to change much. (If it changes a lot, you'll have to re-do this workaround each time.)
Workaround: Manually create the schema file if you are familiar with TSVN:
1. Check out the repository to a working folder (You can right-click on the URL on the Setup Tab and copy it.)
2. In the Security\Schemas directory, create a text file and rename it to dbo.sql
3. Paste in the text from the db version diff pane on the Commit Tab (You can right-click on the diff pane Select All, right-click again and copy.)
This was:
-- Permissions
GRANT VIEW DEFINITION ON SCHEMA:: [dbo] TO [cy_reader]
GO
4. Remove the "-- Permissions" and the empty line from the top of the file
5. Save the file
6. Use TSVN to Add and Commit this change back to the repository
7. In SSMS, refresh your commit list
The dbo schema should no longer appear on the commit list.
Add comment
Please sign in to leave a comment.
Due to this, the dbo schema always wants to load into source control, but when you try to load it into source control, an error is thrown likely because the program explicitly ignores the dbo schema and it doesn't see any changes that need to be made (The error says "The array must contain at least one element").
I've sent the error report, but I thought I'd bring it up here since I'm sure others will encounter this soon.