| Author |
Topic |
|
gbatta
Starting Member
26 Posts |
 Posted - 2006-05-24 : 10:27:08
|
| Hi,I have a DTS package that runs a series of subordinate DTS packages in a certain sequence to copy data from a production to a development server. This package has been running for over a year perfectly fine; however, now I am getting an error that states "The number of failing rows exceeds the mazimum specified. (Microsoft OLE DB Provider for SQL Server (80004005): Unspecified error)" when the main DTS package calls one of the subordinate packages.I have not made any permission, structure or data type changes to the table it is erroring on; therefore, I am a bit stumped at why I am receiving this error all of the sudden. I have had suggestions from this board that I simply do away with the copying via DTS and just BACKUP/RESTORE from the production files. While this is an option, I first want to figure out why this error is occuring and find a fix for it.If anyone has any thoughts, please let me know.Thank you in advance!Ginger |
|
|
gbatta
Starting Member
26 Posts |
Posted - 2006-05-24 : 11:05:07
|
| It may help for me to mention that when I run the subordinate DTS package alone, it works just fine and the sequence in which the subordinate DTS packages are called in the main package does not have any PK violations.Thank you. |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-24 : 21:22:56
|
run the subordinate packages in sequence simulating your dts package workflow... see if that gives you a clue --------------------keeping it simple... |
|
|
|
gbatta
Starting Member
26 Posts |
Posted - 2006-05-25 : 08:34:45
|
| I have done that, and everything runs fine. It is just in the workflow that the one subordinate package fails.I am completely stumped on this one... |
|
|
|
gbatta
Starting Member
26 Posts |
Posted - 2006-05-25 : 10:26:17
|
| I have narrowed the problem down to two columns in the table I am trying to copy that have the data type "smalldatetime". Like I said before, I have not changed anything in this table, so I am unsure why this all of the sudden would create an error in the DTS package. |
|
|
|
gbatta
Starting Member
26 Posts |
Posted - 2006-05-25 : 10:48:17
|
| Scratch my last post. If I run the whole subordinate package from the main workflow package, it fails. If in the subordinate package I run everything except the 2 columns with the data type "smalldatetime" it runs fine. If in the subordinate package I run only the 2 columns with the data type "smalldatetime" it runs fine. I am not seeing any commonality between these cases that would point me in the right direction to get this fixed... |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-25 : 21:56:55
|
| look into constraints that may be invoking the failure on some records on those two columns, since it's a workflow, is it possible that there are some pk or fk violations being made on some records?--------------------keeping it simple... |
|
|
|
gbatta
Starting Member
26 Posts |
Posted - 2006-05-26 : 07:51:28
|
| I have checked into all possible violations and that doesn't seem to be the problem. Here are the symptoms:1. If I execute all columns in the subordinate package, it fails.2. If I execute all columns but those with the data type "smalldatetime", it succeeds.3. If I execute only the 2 columns of "smalldatetime", it succeeds.I have other packages that run with the same data types, but they are not causing errors. |
|
|
|
|
DTS error - "The number of failing rows..."