Comments
3 comments
-
Hello,
Is the jobecode column also an int datatype in the second database? -
As usual, 5 minutes after posting this question I figured out the problem was on my end. The "jobcode" column in the target database was spelled "jobecode". After fixing this, the data synch ran correctly. I guess the moral of the story is to run SQLCompare before Data Compare.
-
No problem! :-)
Add comment
Please sign in to leave a comment.
CREATE TABLE [dbo].[jobcodes]
(
[Jobcodeid] [int] NOT NULL IDENTITY(1, 1),
[jobecode] [int] NOT NULL,
[JobcodeDesc] [nvarchar] (200) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL
)
I wanted to synch the data in this table between two databases. Data Compare's script came out looking like:
INSERT INTO [dbo].[jobcodes] ([Jobcodeid], [JobcodeDesc]) VALUES (1, N'Administrative Services- Entry')
Notice that the script does not include the "jobecode" column. And since this column cannot be null, the script fails.
I was wondering if anyone could tell me why this column is not being included in the script.
TIA