Options
Should RedGateDatabaseInfo.xml be versioned or not?
Rustyf90210
Posts: 2 New member
Hi there
What's the official line with RedGateDatabaseInfo.xml? Should it be versioned or left as a local artifact for each developer? We're getting merge conflicts on developer-specific details. A quick google suggests some check it in and others don't (as apparently, Compare re-creates the file if missing).
What's the official line with RedGateDatabaseInfo.xml? Should it be versioned or left as a local artifact for each developer? We're getting merge conflicts on developer-specific details. A quick google suggests some check it in and others don't (as apparently, Compare re-creates the file if missing).
Tagged:
Answers
Thanks for reaching out to us regarding this.
The official advise is to leave/ignore the RedGateDatabaseInfo.xml file. It contains information that the comparison engine uses and so it is also recommended to not delete of modify it (as mentioned: https://documentation.red-gate.com/sdc10/working-with-other-data-sources/working-with-scripts-folders#:~:text=The file RedGateDatabaseInfo.,delete or modify these files).
I hope this helps!
Dan Jary | Redgate Software
Have you visited our Help Center?
So does that mean don't check in the file into version control? Ignore from version control? It still not clear in the docs.
Most customers using SQL Source Control (which I take it is the case here?) do include this file with their source control project, but ignore it's there.
I will raise this with the development team to get the documentation around this reviewed.
Dan Jary | Redgate Software
Have you visited our Help Center?
As part of our development teams' investigation around what is documented for RedGateDatabaseInfo.xml, they have asked for some more detail around the merge conflicts you were seeing. Are you able to provide any further detail on this?
Dan Jary | Redgate Software
Have you visited our Help Center?