Data Extraction Program within SQL Reporting Svcs

I have installed SQL Reporting Services and have been trying to implement the
Report Pack for SharePoint Portal Server that was recently released. Part of
the VERY limited instructions that comes with the Report Pack states that you
can import your existing SPS log files using the Data Extraction Program
(DEP).
I have tried this a number of times now and the SPS logs will import into
dbSPSReportingStaging with no errors. However, when the application attempts
to move those logs from dbSPSReportingStaging to dbSPSReporting I get an
error message "String or binary data would be truncated" and the statement
terminates without moving the data into dbSPSReporting.
Obviously (to me anyway) there is a field that is not of sufficient length
(or perhaps the wrong type) in dbSPSReporting. Given the fact that this DB is
created using a .sql script written and included in the Report Pack how can I
identify which field is causing the problem and fix it?
Any help is appreciated!
TIAMark Harrison pointed me to the link below which should fix the issue
http://blogs.msdn.com/dinod/archive/2005/08/19/453724.aspx
"Jay" wrote:
> I have installed SQL Reporting Services and have been trying to implement the
> Report Pack for SharePoint Portal Server that was recently released. Part of
> the VERY limited instructions that comes with the Report Pack states that you
> can import your existing SPS log files using the Data Extraction Program
> (DEP).
> I have tried this a number of times now and the SPS logs will import into
> dbSPSReportingStaging with no errors. However, when the application attempts
> to move those logs from dbSPSReportingStaging to dbSPSReporting I get an
> error message "String or binary data would be truncated" and the statement
> terminates without moving the data into dbSPSReporting.
> Obviously (to me anyway) there is a field that is not of sufficient length
> (or perhaps the wrong type) in dbSPSReporting. Given the fact that this DB is
> created using a .sql script written and included in the Report Pack how can I
> identify which field is causing the problem and fix it?
> Any help is appreciated!
> TIA