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

dangerous or heavy queries faster in front of me

Dear fellows,
I'd like to implement any kind of task or mechanism which to capture all
those queries greater than x minutes. An alarm system which inform me of inf
o
such as spid, loginname, and so on and in order to avoid that, from time to
time do sp_who_3 for obtain critical information from my QA against the
production's servers.
Any thought, idea or advice would be great!
Best regards,you can use the query governor
for long running queries
however you can also design a trace with sql server profiler to capture long
running queries
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"Enric" wrote:

> Dear fellows,
> I'd like to implement any kind of task or mechanism which to capture all
> those queries greater than x minutes. An alarm system which inform me of i
nfo
> such as spid, loginname, and so on and in order to avoid that, from time t
o
> time do sp_who_3 for obtain critical information from my QA against the
> production's servers.
> Any thought, idea or advice would be great!
> Best regards,|||Thanks for your input Jose.
In a fact I use the profiler and obtaining for example the number of queries
commited in a hour filtering by loginname (of course, after have been done a
dump to a sql table from Profiler app) but I am righ now looking for is some
a little bit different. Just an alarm automatically which will arise when a
query were spending too many time or resources
"Jose G. de Jesus Jr MCP, MCDBA" wrote:
> you can use the query governor
> for long running queries
> however you can also design a trace with sql server profiler to capture lo
ng
> running queries
>
>
> --
> Jose de Jesus Jr. Mcp,Mcdba
> Data Architect
> Sykes Asia (Manila philippines)
> MCP #2324787
>
> "Enric" wrote:
>|||Enric wrote:
> Dear fellows,
> I'd like to implement any kind of task or mechanism which to capture
> all those queries greater than x minutes. An alarm system which
> inform me of info such as spid, loginname, and so on and in order to
> avoid that, from time to time do sp_who_3 for obtain critical
> information from my QA against the production's servers.
> Any thought, idea or advice would be great!
> Best regards,
SQL Profiler has a template to enable you to do exactly what you need
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.|||SQLProfilerTSQL_Duration.tdf
Thanks in advance,
"Bob Barrows [MVP]" wrote:

> Enric wrote:
> SQL Profiler has a template to enable you to do exactly what you need
> --
> Microsoft MVP -- ASP/ASP.NET
> Please reply to the newsgroup. The email account listed in my From
> header is my spam trap, so I don't check it very often. You will get a
> quicker response by posting to the newsgroup.
>
>|||You can setup and alert to notify you via email, pager, or net message when
an event reaches a specific threshold. There are events related to system
performance.
http://msdn.microsoft.com/library/d... />
p_3kx5.asp
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:2C3A3DDF-05BA-44D2-B62E-DDB38434C762@.microsoft.com...
> Dear fellows,
> I'd like to implement any kind of task or mechanism which to capture all
> those queries greater than x minutes. An alarm system which inform me of
> info
> such as spid, loginname, and so on and in order to avoid that, from time
> to
> time do sp_who_3 for obtain critical information from my QA against the
> production's servers.
> Any thought, idea or advice would be great!
> Best regards,