Activity overview
Latest activity by stone
@David Atkinson The source code repository included several databases, and in SSMS when linking a specific database to source control I was only choosing the repository folder and not the database folder under the repository folder. My bad. Once I chose the database folder under the repository folder everything worked! Thanks for responding!! / comments
@David Atkinson The source code repository included several databases, and in SSMS when linking a specific database to source control I was only choosing the repository folder and not the database ...
The repository included several databases, and in SSMS when linking a specific database to source control I was only choosing the repository folder and not the database folder under the repository folder. My bad. / comments
The repository included several databases, and in SSMS when linking a specific database to source control I was only choosing the repository folder and not the database folder under the repository ...
Note 3: I tried deleting the stored procedure '[dbo].[sproc_name]'.from the database I was trying to link source code to, but got the same error for the same sproc. / comments
Note 3: I tried deleting the stored procedure '[dbo].[sproc_name]'.from the database I was trying to link source code to, but got the same error for the same sproc.
Note: The same stored procedure '[dbo].[sproc_name]' is in EVERY database on the server instance. / comments
Note: The same stored procedure '[dbo].[sproc_name]' is in EVERY database on the server instance.
"A duplicate definition was found for the stored procedure '[dbo].[sproc_name]'.
What can I do about this Redgate error received when I try to link a database to source control? "A duplicate definition was found for the stored procedure '[dbo].[sproc_name]'.
cperez, I have been incorrect in my assessment. The table in question has an int identity column as the PK, and I was not aware the prod and test were manually populated, instead of using the Data Compare to move the new rows from test to prod, and also that test and prod have never been in sync for this table. The new rows in test did show up under the "in both but different" tab due to the new PKs in test were already in prod. Thank you for your time. This was my 1st post to a Redgate forum and I am impressed with the helpfulness. / comments
cperez, I have been incorrect in my assessment. The table in question has an int identity column as the PK, and I was not aware the prod and test were manually populated, instead of using the Data...
[image] [image] cperez, as I cannot show company data this is the best I can do. In the image above, TABLE_A is the system-versioned table in the production database, and when the table is compared to the same table in the test database I do not see the extra 6 rows in the "Only in right" tab (prod on left, test on right). Make sense? / comments
cperez, as I cannot show company data this is the best I can do. In the image above, TABLE_A is the system-versioned table in the production database, and when the table is compared to the same ta...
version 15.3.6.25729 Professional / comments
version 15.3.6.25729 Professional
Data Compare not working with system-versioned tables
Data Compare not working with system-versioned tables. Comparison results are shown but they are incorrect.