Comments
Sort by recent activity
Just
removing the files from transient folder as suggested by Redgate earlier was
not working.
The
following process worked: Unlink Source code control; Remove the files (that
were showing up as duplicate files in the logs) from the local repository and
then commit the change to GitHub to remove the files from GitHub, and then link
source code control.
I still
do not understand why removing a table and creating view with same name caused
Redgate SQL Source Control to go Topsy Turvy, while the operation was valid for
the database. Suggesting to start a new repository was a bad idea, as we would
lose all the change history. Please get to the root cause of the problem to
resolve this for future.
After
that resolution, hundreds of objects appeared as Change Type “Conflict”, I had to select each one to set “Keep Mine”. Why
can’t I bulk select and set “Keep Mine”? The product seems very unstable,
and needs some serious updates, especially the version to work with GitHub. / comments
Just
removing the files from transient folder as suggested by Redgate earlier was
not working.
The
following process worked: Unlink Source code control; Remove the files (that
were showing up as ...
Just
removing the files from transient folder as suggested by Redgate earlier was
not working.
The
following process worked: Unlink Source code control; Remove the files (that
were showing up as duplicate files in the logs) from the local repository and
then commit the change to GitHub to remove the files from GitHub, and then link
source code control.
I still
do not understand why removing a table and creating view with same name caused
Redgate SQL Source Control to go Topsy Turvy, while the operation was valid for
the database. Suggesting to start a new repository was a bad idea, as we would
lose all the change history. Please get to the root cause of the problem to
resolve this for future.
After
that resolution, hundreds of objects appeared as Change Type “Conflict”, I had to select each one to set “Keep Mine”. Why
can’t I bulk select and set “Keep Mine”? The product seems very unstable,
and needs some serious updates, especially the version to work with GitHub.
/ comments
Just
removing the files from transient folder as suggested by Redgate earlier was
not working.
The
following process worked: Unlink Source code control; Remove the files (that
were showing up as ...
As suggested, I have deleted the following files from the transient folder. I double checkd the transient folder for all these files after deletion and di not find them. Bur when I re-run the Commit for KPGA_DWH database, the files come back and I still get the same error. Still waiting for a resolution to this problem. A table can be dropped in a database, and a view can be created by the same name, as the table that was dropped. Why can't Redgate SSC handle this? Files deleted from Transient/Tables folder member.DimMemberFlags.sql member.FactMembershipActive.sql member.FactMembershipCancel.sql member.FactMembershipBroker.sql member.DimMemberCodes.sql / comments
As suggested, I have deleted the following files from the transient folder. I double checkd the transient folder for all these files after deletion and di not find them. Bur when I re-run the Commi...
Here is what I found. Please let me know how I can resolve
this, and why this is an issue.
All of the objects copied below were tables in the old legacy
model. We did some re-modeling and created new objects using our standard
naming convention. Now the tables have a
postfix ‘Tbl’ with the same name and they each have a view without the ‘Tbl’. I think that is causing the duplicate file
issue.
This change is valid in the database, so why does Redgate have an
issue with this. The old tables are in ‘Tables’ folder and the new views with
same name are in the ‘Views’ folder. Why is it comparing tables with views?
Old model tables:
member.DimMemberFlags member.FactMemberShipCancel member.FactMembershipActive member.DimMemberCodes
New Model tables:
member.DimMemberFlagsTbl member.FactMemberShipCancelTbl member.FactMembershipActiveTbl member.DimMemberCodesTbl
New Model views:
member.DimMemberFlags member.FactMemberShipCancel member.FactMembershipActive
member.DimMemberCodes / comments
Here is what I found. Please let me know how I can resolve
this, and why this is an issue.
All of the objects copied below were tables in the old legacy
model. We did some re-modeling and created...
Can I get an appointment this today? I am available 3 pm est onwards or between 10 am est and noon.. / comments
Can I get an appointment this today? I am available 3 pm est onwards or between 10 am est and noon..
The names of tables and views are not same. That's not even possible in the same database. The Tables have a 'TBL' postfix and the views are without that. This is our naming convention from the very beginning. All tables and views are named that way, and SSC was working with it. I suspects the problem to be something else. Please set up a meeting so you can look into it and resolve quickly. I have attached the snapshots in a zip folder to show the mane differences. / comments
The names of tables and views are not same. That's not even possible in the same database. The Tables have a 'TBL' postfix and the views are without that. This is our naming convention from the ver...
transient file attached / comments
transient file attached
I looked in the logs and also in my repository. All the objects that show RedGate.SQLCompare.Engine.DuplicateObjectNameException have only one copy in the GitHub repository and have been checked in by me using SQL Source Control. I am attaching logs, working base and transient files zip files as requested. Please help resolve this ASAP.[image] [image] / comments
I looked in the logs and also in my repository. All the objects that show RedGate.SQLCompare.Engine.DuplicateObjectNameException have only one copy in the GitHub repository and have been checked in...
logs file attached / comments
logs file attached
Tianjiao_Li said:
Hi @mbourgon @kalo SQL Source Control always asks to acknowledge any warning that the Compare engine is generating in order to proceed with committing. If you Ignore "Filegroups, partition schemes and partition functions" in the Comparison options, you will stop getting this warning. If not, unfortunately you need to manually accept the warning every time you commit.
How do I set it to ignore "Filegroups, partition schemes and partition functions" in the Comparison options? where is that setting. I didnt ind it is sql source control setup and options. Thanks. / comments
Tianjiao_Li said:
Hi @mbourgon @kalo SQL Source Control always asks to acknowledge any warning that the Compare engine is generating in order to proceed with committing.If you Ignore "Filegro...