Comments
6 comments
-
I have also received this error this morning - strange because everything seemed to be working OK on Friday afternoon.
I am fully up-to-date with Windows updates, and have tried rolling back to v1.1. Other developers attaching to the same SVN repository are having the same issue.
I created a new SVN folder and linked my database to it. This worked for a while and then came back with the same error.
My instance default collation is Latin1_General_CI_AS, my db collation is SQL_Latin1_General_CP1_CI_AS.
The error only happens on 1 of my SourceControl db's.
What exactly does 'Ensure that case sensitivity options are set correctly and all object creation scripts are valid' mean and how can I proceed?
Windows 7 Pro SP1 x64, SQL Server 2008, SVN, SQL Source Control 2.1.0.31 (I recently updated to the 14 day trial of this) -
This error will generally occur if there are multiple files that contain the create SQL for the object in question within your SVN repo.
This can occur if a developer makes a backup of a script in SVN for instance - as SQL Source Control parses the whole folder structure, if there is more than one file that "creates" an object, then it doesn't know which to use and you get the error. It can also occur if a file has multiple object creation statements.
So, you need to check through your repo for any files that may reference the object the error refers to and remove the invalid ones.
You'll also then need to check your workingbases and transients for the same thing (or just unlink + relink which should give you new sets of those) -
Thanks for the response, this was indeed the problem.
-
Thanks james, I tried to unlink and relink the database, it solved my problem. But i guess, the problem started when i changed the schema of a SP.
Will try to do the same things i did before the source control crashed and will let you know if thats causing the problem.
Vijay -
As a follow up to this; I automatically create a "CreateDatabaseObjects.sql" script from the SourceControl db object scripts in SVN. The create objects script was in the database directory that SourceContol is linked to and I think that SourceContol found it and threw the duplicate objects error.
-
Yes, that would almost certainly be it. If you are going to have extra "maintenance" scripts they need to be stored above the folder you're linking to, otherwise SQL Source Control will try to parse it and you'll encounter this kind of problem.
Add comment
Please sign in to leave a comment.
SQL Source control gave me this error, after i commited couple of new SP's and Tables to the source control.
My environment:
SQL Server 2008, Sourcegear Vault Professional, SQL Source Control 2.1.0.31
I've already reported about this error through the SQL Source Control error reporting tool, but haven't received any response to it.
Following is the complete error details,
Let me know if you need any further information, as i need this thing to be resolved as quickly as possible.
Thanks,
Vijay