Specify Tables Whose Data ... - Not All Tables Listed

Packages and compresses schema and contents of SQL Server databases

Moderators: JonathanWatts, Chris Auckland, David Atkinson, david connell, Anu Deshpande, Michelle Taylor, james.billings, Marianne

Specify Tables Whose Data ... - Not All Tables Listed

Postby MarkEaston » Fri Oct 09, 2009 2:44 am

We have just purchased and installed the latest version of Red Gate SQL Comparison Bundle.

I am trying to package a database upgrade, but all the data tables that need to be upgraded are NOT displaying. Some are though. I cannot determine why some are and some are not. For instance I have a table called ButtonLookup in the new db and also in the db to be upgraded. They are identical. The one in the new db has data and the one in the old db does not. So, this should result in data being inserted in to the table in the old db. But the table is not even listed in the data packager. Why is that?

Here are the structures of the two tables. They look identical to me ...

New DB:

USE [DR]
GO
/****** Object: Table [dbo].[ButtonLookup] Script Date: 10/09/2009 14:31:08 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
CREATE TABLE [dbo].[ButtonLookup](
[PropertyID] [int] NOT NULL CONSTRAINT [DF_ButtonLookup_PropertyID] DEFAULT (0),
[TblName] [varchar](128) COLLATE SQL_Latin1_General_CP1_CI_AS NULL CONSTRAINT [DF_ButtonLookup_TblName] DEFAULT (' '),
[FldName] [varchar](128) COLLATE SQL_Latin1_General_CP1_CI_AS NULL CONSTRAINT [DF_ButtonLookup_FldName] DEFAULT (' '),
[IDFld] [varchar](128) COLLATE SQL_Latin1_General_CP1_CI_AS NULL CONSTRAINT [DF_ButtonLookup_IDFld] DEFAULT (' '),
[Depend] [varchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL CONSTRAINT [DF_ButtonLookup_Depend] DEFAULT (' ')
) ON [PRIMARY]

GO
SET ANSI_PADDING OFF


Old DB:

USE [QVisual58]
GO
/****** Object: Table [dbo].[ButtonLookup] Script Date: 10/09/2009 13:29:37 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
CREATE TABLE [dbo].[ButtonLookup](
[PropertyID] [int] NOT NULL CONSTRAINT [DF_ButtonLookup_PropertyID] DEFAULT ((0)),
[TblName] [varchar](128) COLLATE SQL_Latin1_General_CP1_CI_AS NULL CONSTRAINT [DF_ButtonLookup_TblName] DEFAULT (' '),
[FldName] [varchar](128) COLLATE SQL_Latin1_General_CP1_CI_AS NULL CONSTRAINT [DF_ButtonLookup_FldName] DEFAULT (' '),
[IDFld] [varchar](128) COLLATE SQL_Latin1_General_CP1_CI_AS NULL CONSTRAINT [DF_ButtonLookup_IDFld] DEFAULT (' '),
[Depend] [varchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL CONSTRAINT [DF_ButtonLookup_Depend] DEFAULT (' ')
) ON [PRIMARY]

GO
SET ANSI_PADDING OFF
MarkEaston
 
Posts: 2
Joined: Fri Oct 09, 2009 2:31 am

Comparison Key

Postby MarkEaston » Fri Oct 09, 2009 3:50 am

If the problem is with the lack of a comparison key ... then how in Packager do I specify a comparison key for such a table? I can see how to do this in the SQL Compare but not in SQL Packager.
MarkEaston
 
Posts: 2
Joined: Fri Oct 09, 2009 2:31 am

Postby Chris Auckland » Mon Oct 12, 2009 3:20 pm

Thanks for your post.

Your suspicions are correct, the problem is that there isn't a way to set a custom comparison key using SQL Packager 6. We will eventally add this facility (feature code: SPA-462), but it's not possible in the current version.

The best workaround we can ofer at present will be to create the migration scripts using SQL Compare and SQL Data Compare. You can then combine them into a single file, then package the script using SQL Packager.

I hope this is helpful.
Chris
Chris Auckland
 
Posts: 757
Joined: Tue Oct 24, 2006 2:12 pm
Location: Red Gate Software Ltd.


Return to SQL Packager 6

Who is online

Users browsing this forum: No registered users and 0 guests