Data Issues

I have a static report that has 2 parameters begin date and end date. The
report has been running fine for several months but today we had a major data
problem. The query returns dollar amounts based on sales, When running the
report for 12/29/204 to 1/5/05 we received 3 million in sales, which we knew
was incorrect. We then queried the tables directly through PL/SQL developer
and came up with the correct numbers. We then stopped and started the
reporting service's service and reposted the report but we came back with the
bad sales number. Out of curiosity I ran the report for dates in the future
such as 1/10/05, 1/15/05 etc. and came back with sales numbers. Again I
checked the tables were hitting and of course their was no data. This was all
in the morning. I just ran the report again this afternoon and now it is
correct. Does anyone have a clue as to why this might be happening?Is the report cached or run on a schedule?..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Zach" <Zach@.discussions.microsoft.com> wrote in message
news:391A179E-B8F2-4E62-81D6-7FF4ED92C9D1@.microsoft.com...
> I have a static report that has 2 parameters begin date and end date.
The
> report has been running fine for several months but today we had a major
data
> problem. The query returns dollar amounts based on sales, When running
the
> report for 12/29/204 to 1/5/05 we received 3 million in sales, which we
knew
> was incorrect. We then queried the tables directly through PL/SQL
developer
> and came up with the correct numbers. We then stopped and started the
> reporting service's service and reposted the report but we came back with
the
> bad sales number. Out of curiosity I ran the report for dates in the
future
> such as 1/10/05, 1/15/05 etc. and came back with sales numbers. Again I
> checked the tables were hitting and of course their was no data. This was
all
> in the morning. I just ran the report again this afternoon and now it is
> correct. Does anyone have a clue as to why this might be happening?|||No. The end user just clicks on the report and keys in the begin and end
dates.
"Wayne Snyder" wrote:
> Is the report cached or run on a schedule?..
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Zach" <Zach@.discussions.microsoft.com> wrote in message
> news:391A179E-B8F2-4E62-81D6-7FF4ED92C9D1@.microsoft.com...
> > I have a static report that has 2 parameters begin date and end date.
> The
> > report has been running fine for several months but today we had a major
> data
> > problem. The query returns dollar amounts based on sales, When running
> the
> > report for 12/29/204 to 1/5/05 we received 3 million in sales, which we
> knew
> > was incorrect. We then queried the tables directly through PL/SQL
> developer
> > and came up with the correct numbers. We then stopped and started the
> > reporting service's service and reposted the report but we came back with
> the
> > bad sales number. Out of curiosity I ran the report for dates in the
> future
> > such as 1/10/05, 1/15/05 etc. and came back with sales numbers. Again I
> > checked the tables were hitting and of course their was no data. This was
> all
> > in the morning. I just ran the report again this afternoon and now it is
> > correct. Does anyone have a clue as to why this might be happening?
>
>|||It's that pesky Y2K005 issue...
Can you run a trace of the SQL activity, and check what is being passed as
parameters? Are the dates being processed as strings?
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Zach" <Zach@.discussions.microsoft.com> wrote in message
news:391A179E-B8F2-4E62-81D6-7FF4ED92C9D1@.microsoft.com...
>I have a static report that has 2 parameters begin date and end date.
>The
> report has been running fine for several months but today we had a major
> data
> problem. The query returns dollar amounts based on sales, When running
> the
> report for 12/29/204 to 1/5/05 we received 3 million in sales, which we
> knew
> was incorrect. We then queried the tables directly through PL/SQL
> developer
> and came up with the correct numbers. We then stopped and started the
> reporting service's service and reposted the report but we came back with
> the
> bad sales number. Out of curiosity I ran the report for dates in the
> future
> such as 1/10/05, 1/15/05 etc. and came back with sales numbers. Again I
> checked the tables were hitting and of course their was no data. This was
> all
> in the morning. I just ran the report again this afternoon and now it is
> correct. Does anyone have a clue as to why this might be happening?|||I just took a look at your code in the other thread. You're creating
heartache for yourself by breaking apart the dates. Wayne gave you good
advice about using the DateAdd function.
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Zach" <Zach@.discussions.microsoft.com> wrote in message
news:391A179E-B8F2-4E62-81D6-7FF4ED92C9D1@.microsoft.com...
>I have a static report that has 2 parameters begin date and end date.
>The
> report has been running fine for several months but today we had a major
> data
> problem. The query returns dollar amounts based on sales, When running
> the
> report for 12/29/204 to 1/5/05 we received 3 million in sales, which we
> knew
> was incorrect. We then queried the tables directly through PL/SQL
> developer
> and came up with the correct numbers. We then stopped and started the
> reporting service's service and reposted the report but we came back with
> the
> bad sales number. Out of curiosity I ran the report for dates in the
> future
> such as 1/10/05, 1/15/05 etc. and came back with sales numbers. Again I
> checked the tables were hitting and of course their was no data. This was
> all
> in the morning. I just ran the report again this afternoon and now it is
> correct. Does anyone have a clue as to why this might be happening?