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

Damaged databases

Hi

I recently had a hard disk failure on which was running Win2003 SQL2000 SP4.

This server is a sharepoint backend server, I repaired the disk to the point that it could be mirrored across to a new and then set about looking at the databases. There was a schedule in place to backup all 4 DBs daily, the backup process at no time after verifying the backup had any errors. All but one of the DBs reports this error when I attempt to run DBCC or similar query I/O error (bad page ID) detected during read at offset etc. (error 823) I have restored back to the earliest DBs I have and I still get the same error.

Any ideas on how I can recover as much as possible if not all of the DBs? What is the best way to restore from a transaction log? I have found a few articles on it and they all take a slightly different approach for differnet situations however I'm not entirely sure which applies to me.

All help will be very much appreciated.

Rob

Sounds like your backups are corrupt too - I suspect that the disk hardware was going bad for a while and all the backups have backed up corrupted data. Does the backup process backup the databases to the same disk hardware? How often do you run DBCC CHECKDB on your databases to verify their integrity?

You can't recover from just a transaction log - you need to restore a full backup first. What's the DBCC error you get (post the output of "DBCC CHECKDB (yourdb) WITH ALL_ERRORMSGS, NO_INFOMSGS")? Your only option may be to extract what data you can into a new database.

Thanks

Damaged databases

Hi

I recently had a hard disk failure on which was running Win2003 SQL2000 SP4.

This server is a sharepoint backend server, I repaired the disk to the point that it could be mirrored across to a new and then set about looking at the databases. There was a schedule in place to backup all 4 DBs daily, the backup process at no time after verifying the backup had any errors. All but one of the DBs reports this error when I attempt to run DBCC or similar query I/O error (bad page ID) detected during read at offset etc. (error 823) I have restored back to the earliest DBs I have and I still get the same error.

Any ideas on how I can recover as much as possible if not all of the DBs? What is the best way to restore from a transaction log? I have found a few articles on it and they all take a slightly different approach for differnet situations however I'm not entirely sure which applies to me.

All help will be very much appreciated.

Rob

Sounds like your backups are corrupt too - I suspect that the disk hardware was going bad for a while and all the backups have backed up corrupted data. Does the backup process backup the databases to the same disk hardware? How often do you run DBCC CHECKDB on your databases to verify their integrity?

You can't recover from just a transaction log - you need to restore a full backup first. What's the DBCC error you get (post the output of "DBCC CHECKDB (yourdb) WITH ALL_ERRORMSGS, NO_INFOMSGS")? Your only option may be to extract what data you can into a new database.

Thanks

Customizing Report Viewer Webpart of SQL Reporting Services in integration mode in MOSS200

Hi All,
I do have a question about the report viewer web part in SharePoint 2007 /
SharePoint Services 3.0. We like to have a custom report parameter section,
is it possible to modify or extend the SharePoint Report Viewer web part? Or
do we have to create one ourselves. If so, have can we do that, how does the
webpart technically work.. I need some hints on how to start.If I wrote my
own Report Viewer webpart, how must it connect to the Report List web part
etc?
Kind regards,Petersee this at :
http://blogs.sqlxml.org/bryantlikes/articles/628.aspx
Not sure whether its has a parameter section
But this one should have at : http://aspalliance.com/729
Hope that helps
Patrick
"Peter Bons" <Peter@.giessen.nl> wrote in message
news:EE1C71F9-931C-48F8-A916-613F2AABD5C5@.microsoft.com...
> Hi All,
> I do have a question about the report viewer web part in SharePoint 2007 /
> SharePoint Services 3.0. We like to have a custom report parameter
> section, is it possible to modify or extend the SharePoint Report Viewer
> web part? Or do we have to create one ourselves. If so, have can we do
> that, how does the webpart technically work.. I need some hints on how to
> start.If I wrote my own Report Viewer webpart, how must it connect to the
> Report List web part etc?
> Kind regards,
>|||As far as I can tell, the Report Viewer web part simply creates an IFRAME
and creates a URL to render the report within it.
It implements the web part interface that allows it to accept connections
and when you connect the Report List web part to it, it gets the report name
from the Report List web part to use in creating the URL.
Creating your own Report Viewer web part should be fairly simple. You just
need to build a URL and render it in the IFRAME. There are examples of this
on the web - I think one was referenced in another post.
The options you can set in a URL can be found here:
http://msdn2.microsoft.com/en-us/library/ms152835.aspx
"Peter Bons" <Peter@.giessen.nl> wrote in message
news:EE1C71F9-931C-48F8-A916-613F2AABD5C5@.microsoft.com...
> Hi All,
> I do have a question about the report viewer web part in SharePoint 2007 /
> SharePoint Services 3.0. We like to have a custom report parameter
> section, is it possible to modify or extend the SharePoint Report Viewer
> web part? Or do we have to create one ourselves. If so, have can we do
> that, how does the webpart technically work.. I need some hints on how to
> start.If I wrote my own Report Viewer webpart, how must it connect to the
> Report List web part etc?
> Kind regards,
>