User profile for jonswaino

Hi, I've followed what you said, and instead use the 'DESCRIPTION' column of my table as the key from which to compare. I've also set the option on the project to 'Ignore Primart Keys'. When I perform the comparison, and then generate the INSERT scripts, I still get the INSERT statement including the primary key column AND the primary key value. I don't want SQL Data Compare to do anything with the primary key. Is there anyway I am doing this in the wrong way or an alternative solution to this problem. I'm effectively wanting to remove a column from the comparison along with generating any data for that column. ** UPDATE ** I think I've resolved the issue, I just needed to unmap the columns that I wasn't interested in so everything is ok now. Thanks for your help. / comments

Hi, I've followed what you said, and instead use the 'DESCRIPTION' column of my table as the key from which to compare. I've also set the option on the project to 'Ignore Primart Keys'. When I pe...

0 votes

Hi, I think I found the cause of the problem so this issue can be closed down. When I do a compare of the database against scripts, there is a SqlCompareDatabaseInfo.xml and a RedGateDatabaseInfo.xml file in the root of the path. I'm not sure why I have this files, and also it seems that sourcesafe sees that these files are always different when getting the latest version. As SQL Compare is set to check-out files immediately, source safe prompts for whether these fails should be overwritten with the server versions. This prompt is displayed but hidden behind the SQL Compare dialog box which means that it looks like SQL compare is hanging. It isn't - its just that SQL compare is waiting on sourcesafe to complete, and sourcesafe is waiting for a prompt for the user. Because the dialog is hidden, its not evident that sourcesafe is awaiting a response. The solution is to shuffle/minimise windows to try and get to the dialog box. Maybe sql compare's dialog could be positioned behind or force sourcesafe dialog to come to the top. / comments

Hi, I think I found the cause of the problem so this issue can be closed down. When I do a compare of the database against scripts, there is a SqlCompareDatabaseInfo.xml and a RedGateDatabaseInfo.x...

0 votes

After some thought on this, the best way forward for us is to carry out the migration to our db schema scripts stored in source control. Backup our live database, clear out any old data from the database, and then carryout an automatic build of our schema to the live database. We could then create some manual scripts to then copy the data from the backup database into the new schema. We might be able to do this using SQL Data Compare. If not, we could just restore the database to a different database, and then either copy from that database, or copy the old tables with data into same tables tagged with '_old'. We could then create manual migration scripts to copy the data from the old tables to the new. It might be worth investigating the possibility of allowing columns to be mapped if this problem arises, similar to SQL Data Compare. However, I don't know how this would fit into an automated build scenario. A migration folder which stores these mappings? / comments

After some thought on this, the best way forward for us is to carry out the migration to our db schema scripts stored in source control. Backup our live database, clear out any old data from the d...

0 votes

Just an update, I've been looking at this all today and still not got anywhere. This is not so much a problem with Primary Keys (as the title suggests). Its more a problem with the foreign key, although I removed the constraint so its just like a regular column to try and investigate what is causing the problem. I created 2 very simple test databases (TestDB1, TestDB2). Then in each, I created a very simple table (TestTable). Step 1 The table is created like so: CREATE TABLE [dbo].[TestTable]( [Id] [bigint] IDENTITY(1,1) NOT NULL, [Name] [nchar](10) COLLATE Latin1_General_CI_AS NULL, [CustomerId] [int] NOT NULL, CONSTRAINT [PK_TestTable] PRIMARY KEY CLUSTERED ( [Id] ASC )WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY] Step 2. Now in my 2nd database I create exactly the same table but instead of having a CustomerId column I renamed it manually to ApplicantId, to simulate me renaming a foreign key (again, I removed the constraints for simplicity so its just like any other regular column), but no NULLs are allowed. Step 3. Run SQL Compare and attempt to sync from TestDB2 to TestDB1. I would expect that SQLCompare tries to select data into a temporary table, drop the table, create the new table and select the data back into it. If the column is in the same location, then the select should select into all the new columns in the correct order. However, SQLCompare gives me the following error: The column [ApplicantId] on table [dbo].[TestTable] must be added but has no default and does not allow NULL values. The table must be rebuilt. If the table contains data then the migration script will not work. To avoid this, add a default to the column or mark it as allowing NULL values. So ok, how do I go about changing the foreign key column name without adding a column and allow NULLs? We have a build system, and everything is checked out from source safe. SQL compare then syncs from a scripts folder to the database. We need SQLCompare to work in one go without fiddling with data in the database, or creating extra migration scrips. What baffles me is that this error seems to be displayed for any column rename that is peformed whilst it has a NON-NULL policy. Surely this is going to be a big problem. / comments

Just an update, I've been looking at this all today and still not got anywhere. This is not so much a problem with Primary Keys (as the title suggests). Its more a problem with the foreign key, al...

0 votes

How can we help you today?

jonswaino

Comments