User profile for mshiker

Brian, Thanks for the response. I thought I understood what you were saying but I went and tested it and, I'm sorry, but I still must be missing something. It appears that SQL Compare is able to keep the mapping from renaming the column in either database (db1 or db2). I first tried renaming the column in db2 (from first_name to new_first_name) then did a SQL Compare. When I view the difference in the SQL Compare UI for that particular table I see the the old column name in db1 and the new column name in db2 highlighted in blue (indicating there was a change and not a drop on one side and an add on the other). In the generated script I can see where the data is inserted into the temp table with both column names in the correct position indicating the correct mapping: INSERT INTO [dbo].[tmp_rg_xx_Contact]([contact_id], [prefix_id], [first_name], [middle_name], [last_name], [suffix], [preferred_name], [gender_id], [personality_profile_type_id], [ethnicity_id], [birth_date], [birth_month], [file_set_id], [company_id], [create_date], [create_id], [modify_date], [modify_id]) SELECT [contact_id], [prefix_id], [new_first_name], [middle_name], [last_name], [suffix], [preferred_name], [gender_id], [personality_profile_type_id], [ethnicity_id], [birth_date], [birth_month], [file_set_id], [company_id], [create_date], [create_id], [modify_date], [modify_id] FROM [dbo].[Contact] I did not commit that change. Then I tried renaming the column in db1 (from first_name to new_first_name) and did a SQL Compare. When I view the difference in the SQL Compare UI for that particular table I see the the new column name in db1 and the column name in db2 highlighted in blue (indicating there was a change and not a drop on one side and an add on the other). In the generated script I can see the sp_rename: PRINT N'Altering [dbo].[Contact]' GO sp_rename N'[dbo].[Contact].[first_name]', N'new_first_name', 'COLUMN' Are there situations where SQL Compare can do a successful renaming (mapping of old column name to the new name) and there are some more specific situations where I should be concerned? Thansk again, Marc / comments

Brian, Thanks for the response. I thought I understood what you were saying but I went and tested it and, I'm sorry, but I still must be missing something. It appears that SQL Compare is able to ke...

0 votes

Mismatched names in stored procedure

I'm not sure if this is intended behavior in Microsoft's SQL Server Management Studio (SSMS) (2005) or if it is a bug in SQL Compare but here is a situtation we came across this moring that I would...

1 follower 1 comment 0 votes

Brian, I'm not clear of the exact situation you are getting at in your post of Wed Jul 26, 2006 10:02 am. What I'm not clear on is your statement of "but it has no way of knowing yet when a column exists in the second database under a different name". You stated that SQL Compare will drop the old column and create the new one. So, at that point SQL Compare does know that that column now exists. Why would there be an issue with moving the preserved data into that new column? Thanks, Marc / comments

Brian, I'm not clear of the exact situation you are getting at in your post of Wed Jul 26, 2006 10:02 am. What I'm not clear on is your statement of "but it has no way of knowing yet when a column ...

0 votes

How can we help you today?

mshiker

Activity overview