Hi Guys
I woud like to run either a stored procedure before runing the actual
report. The stored procedure will create and update a table and on the second
run the report query will run and produce the report.
Is it possible to achieve this?
Regards
Tofigh> I woud like to run either a stored procedure before runing the actual
> report. The stored procedure will create and update a table and on the
second
> run the report query will run and produce the report.
> Is it possible to achieve this?
I guess your report is scheduled. Just edit the scheduled job and insert a
step that executes the stored procedures before the step that causes the
report to run.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com|||Thanks for the reply, the report is not scheduled. the users will run the
report on demand.
Regards
Tofigh
"Dejan Sarka" wrote:
> > I woud like to run either a stored procedure before runing the actual
> > report. The stored procedure will create and update a table and on the
> second
> > run the report query will run and produce the report.
> >
> > Is it possible to achieve this?
> I guess your report is scheduled. Just edit the scheduled job and insert a
> step that executes the stored procedures before the step that causes the
> report to run.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
>
>|||Then maybe you can use two SPs - one outer that is called from the report
and returns the data, and inside it you first make a call to the second
procedure that prepares the tables.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"TA" <TA@.discussions.microsoft.com> wrote in message
news:9C1789C5-6FF7-469B-888A-6B0E7547F2BA@.microsoft.com...
> Thanks for the reply, the report is not scheduled. the users will run the
> report on demand.
> Regards
> Tofigh
> "Dejan Sarka" wrote:
> > > I woud like to run either a stored procedure before runing the actual
> > > report. The stored procedure will create and update a table and on the
> > second
> > > run the report query will run and produce the report.
> > >
> > > Is it possible to achieve this?
> >
> > I guess your report is scheduled. Just edit the scheduled job and insert
a
> > step that executes the stored procedures before the step that causes the
> > report to run.
> >
> > --
> > Dejan Sarka, SQL Server MVP
> > Associate Mentor
> > www.SolidQualityLearning.com
> >
> >
> >
Showing posts with label runing. Show all posts
Showing posts with label runing. Show all posts
Wednesday, March 28, 2012
Friday, March 23, 2012
Runing 1st report of the day Hangs
Anyone run in to this issue? Seems to abort on the first report, then when
you rerun it, it works fine.
Happens on different reports, no consistency there.Kris,
I don't recall seeing this.
Do you have any scheduled reports?
Is it the first interactive report of the day that hangs? Or the first
scheduled report of the day?
Also, it may be worth specifying which version and/or service pack you
see this on.
Andrew Watt
MVP - InfoPath
On Fri, 14 Oct 2005 09:54:05 -0700, "Kris"
<Kris@.discussions.microsoft.com> wrote:
>Anyone run in to this issue? Seems to abort on the first report, then when
>you rerun it, it works fine.
>Happens on different reports, no consistency there.sql
you rerun it, it works fine.
Happens on different reports, no consistency there.Kris,
I don't recall seeing this.
Do you have any scheduled reports?
Is it the first interactive report of the day that hangs? Or the first
scheduled report of the day?
Also, it may be worth specifying which version and/or service pack you
see this on.
Andrew Watt
MVP - InfoPath
On Fri, 14 Oct 2005 09:54:05 -0700, "Kris"
<Kris@.discussions.microsoft.com> wrote:
>Anyone run in to this issue? Seems to abort on the first report, then when
>you rerun it, it works fine.
>Happens on different reports, no consistency there.sql
Wednesday, March 7, 2012
run access database too slow
I have a access database, the data store in another server. This noon, one of our user is runing the access database too slow. Open the database and search the data, etc. It took a long time to come out, Any body has experience on it, why, we had etrust install on each user machine, is that cause this too slow? Thanks in advance.Is it Access front-end or Access period? If the latter, - wrong forum, though you might get some answers if you're a little bit more specific.
Subscribe to:
Posts (Atom)