How can we help you today? How can we help you today?

Getting an error for a duplicate definition was found for user.... How do I fix this?

Hi all, 

We just implemented SQL Source control in my company. It's hooked up to Azure Devops via Git. We're getting an error that states there's a duplicate definition for a user and to check case sensitivity options etc...

Our databases ae set to case insensitivity, and I confirmed that there's only one user with that name in the database. Now the same user exists in different databses on the same server/instance, but since they're in different dbs that shouldn't cause a problem.

Is it a problem if I delete the folders in the trainsients folder? would that solve the issue or would it reoccur?
Craig Bobchin
0

Comments

3 comments

Sort by
  • Victoria W
    Hi Craigbob

    Please take a look at this article for troubleshooting the duplicate definition error in SQL Source Control:

    https://productsupport.red-gate.com/hc/en-us/articles/4407476864401-Duplicate-definition-troubleshooting-in-SQL-Source-Control
    Victoria W
    0
  • Craigbob
    I did that and could not find any duplicate definitions. I do have the same user created in datbases but there's no create user script duplication that I can find.
    Craigbob
    0
  • Jon_Kirkwood

    Hi,

    Posting an update here with details from the work conducted with our support team directly on this request.

    My understanding a solution has been found for this issue through the following

     

    • Verifying that GIT is in your system/user environmental path
    • Deleted database related folders from the repo & source folder
    • Recreate the database folders in the repo.
    • Re-link databases to repo through SQL Source Control and sync

     

    There was an issue with reconnecting one of the databases

    </code></p><pre class="CodeBlock"><code><p><code>git exited with code: 1

    warning: git-credential-manager-core was renamed to git-credential-manager

    warning: see https://aka.ms/gcm/rename for more information

    This was potentially solved by configuring the git buffer to avoid remote failing.

    Details on solving that available here:

    https://confluence.atlassian.com/stashkb/git-push-fails-fatal-the-remote-end-hung-up-unexpectedly-282988530.html

    Jon_Kirkwood
    0

Add comment

Please sign in to leave a comment.