How to narrow down the failure message



I have a nightly job which copies the entire contents from a Progress (kinda like Oracle) database to a SQL Server 2005 one. Specifically, I look under SQL Server agent in the tree on the left of SSMS, and open it up and expand the Jobs folder. I right-click the job in the list of jobs, select View History, and see the details.

Since I have been here (a few weeks) this job has failed every time. Nobody else who is currently here knows anything about the job. But all agree it needs to not fail.

It has 17 steps, and the last one is the one that fails. that step calls a stored procedure which copies an entire table over.

Here's the error:

Error converting data type DBTYPE_DBTIMESTAMP to datetime. [SQLSTATE 42000] (Error 8114). The step failed.,00:00:32,16,8114,,,,0

===========

So I looked and found 6 fields in the SQL Server DB which are of the datetime datatype. I looked at the source (Progress) database and couldn't see anything weird in the data contained in those fields. Of course, there are 300000 rows, so I didn't see every one. Still, I did some queries where I did a SELECT, sorted by the name of each field, one at a time, and the lowest value and the highest value always seemed normal. So if a row would have been blank, null, or had some garbage data, I would have seen it in my sorted query.

The only thing I could see was that in a couple of the fields, the source DB would have a value like 2/1/2002. In other words, no time, just the date. But I can't imagine that would be a problem.

I am not sure where to go at this point. Is there any way to make a Failure statement pinpoint the exact item that caused the failure? The exact row, the exact value, anything?

.



Relevant Pages

  • Re: Need Help Exporting a Progress Table
    ... apllication connects to a progress database using a Data Direct SQL92 ... In order to stop using this database and just use SQL Server 2005 I ... export delimiter "," tablename. ...
    (comp.databases.progress)
  • Re: Biztalk Server 2004 - Database synchronization
    ... There are cases where these types of problems are well addressed by BizTalk ... > I have a requirement where in I need to synchronize my legacy Progress ... > database to SQL Server. ... > row to get inserted into my SQL Server table as well. ...
    (microsoft.public.biztalk.general)
  • Biztalk Server 2004 - Database synchronization
    ... I have a requirement where in I need to synchronize my legacy Progress ... row to get inserted into my SQL Server table as well. ... various options to access this database from biztalk? ...
    (microsoft.public.biztalk.general)
  • Access to Progress data files from SQL Server
    ... I've got a backup of a Progress 8.3 database that I need to access and ... eventually port into MS SQL Server. ...
    (comp.databases.progress)
  • Re: Counting rows in an SQL table
    ... SQL Server generates the exact same execution plan for either one. ... you don't have to retrieve everything from the database to count it the ...
    (microsoft.public.dotnet.languages.vb)