Is it possible that a DTS job reports success, but isn't?

I created a DTS job and saved it. The query was:

select * from table where date >= '20061024' and insert the results to a
table on another server of identical stucture and name that had no records in
that date range.

I then went to the job and right clicked and selected "run". The job took
45min and reported "success".

When I used QA to see if some of the records were copied, I noticed that one
record did not copy. It is on the source, but not the target.

What am i missing?

btw, I had 3 DTS jobs that I had created at the same time that were to copy
the same block of records (diff tables). I manually ran all 3 jobs at the
same time. All reported success.

Don
SQL 2000

Is there, perhaps, some constraints on the receiving table that may prevent
a non-conforming row from being inserted?

Is that all of the WHERE clause?

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf


"donsql22222" <donsql22222 (AT) discussions (DOT) microsoft.com> wrote

yes, that's all fo the WHERE clause.

Here's the table structure...target and source were the same.

CREATE TABLE [dbo].[tablename] (
[Name] [varchar] (32) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
[Date] [smalldatetime] NOT NULL ,
[TDate] [smalldatetime] NULL ,
[A] [decimal](18, 6) NOT NULL ,
[b] [decimal](18, 6) NOT NULL ,
[C] [decimal](18, 6) NOT NULL ,
[D] [decimal](18, 6) NOT NULL ,
[E] [decimal](18, 6) NULL ,
[F] [smalldatetime] NULL ,
[G] [int] NOT NULL ,
[H] [int] NOT NULL ,
[i] [int] NULL
) ON [PRIMARY]
GO

CREATE UNIQUE CLUSTERED INDEX [IName] ON [dbo].[TABLENAME]([Name],
[Date]) WITH FILLFACTOR = 80 ON [PRIMARY]
GO



"Arnie Rowland" wrote: