Comments
1 comment
-
I'm afraid this is a bug in SQL Compare 7.1; objects are always mapped case-sensitively, rather than using the database case sensitive setting to determine matches. We have an internal build available that fixes this issue, you'll need to contact support@red-gate.com asking for the 7.2 build of SQL Compare.
Simon C
Add comment
Please sign in to leave a comment.
CREATE TABLE [Data].[ActionItems]
(
[Id] [int] NOT NULL IDENTITY(1, 1),
[Description] [varchar] (50) NOT NULL,
[ActionsId] [int] NOT NULL,
[QueriesId] [int] NOT NULL,
[ExecuteOrder] [int] NOT NULL,
[UsePreviousActionItemDataForParameters] [bit] NOT NULL DEFAULT ((0))
)
GO
CREATE TABLE [data].[ActionItems]
(
[Id] [int] NOT NULL IDENTITY(1, 1),
[Description] [varchar] (50) NOT NULL,
[ActionsId] [int] NOT NULL,
[QueriesId] [int] NOT NULL,
[ExecuteOrder] [int] NOT NULL,
[UsePreviousActionItemDataForParameters] [bit] NOT NULL DEFAULT ((0))
)
GO
Notice that the schema names aren't exactly the same. Even so, I tried to create a schema called Data where a schema called data exists, but failed. So, since the schemas are the same according the SQL server, why don't the tables match?
When will the table mapping feature be available?