Execution snapshots not being added to report history

Hello,
I'm trying to generate a snapshot everytime a report is viewed. I've setup
the properties of the report to "Store all report execution snapshots in
history" but no report is being created under the History tab.
The datasource uses hardcoded credentials.
The only thing I have found in the log file that may relate to this is the
following (but it does not consistently occur every time):
INFO: LoadSnapshot: Item with session: [session id], reportPath: [report
path], userName: [my username] not found in the database
Can anyone help?
ThanksDo you have the report set up to run on an Execution snapshot? That setting
is on the Execution subtab (Under the properties tab). If not then no
execution snapshots are being created, so none are being stored.
There is no setting to create a report execution snapshot on each viewing.
Execution snapshots can only be created manually (via the SOAP Api or
checking the check box in Report Manager) or on a schedule.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ian F" <IanF@.discussions.microsoft.com> wrote in message
news:CF1B4CBA-B0B1-4A6B-9433-DE65CB817749@.microsoft.com...
> Hello,
> I'm trying to generate a snapshot everytime a report is viewed. I've
setup
> the properties of the report to "Store all report execution snapshots in
> history" but no report is being created under the History tab.
> The datasource uses hardcoded credentials.
> The only thing I have found in the log file that may relate to this is the
> following (but it does not consistently occur every time):
> INFO: LoadSnapshot: Item with session: [session id], reportPath: [report
> path], userName: [my username] not found in the database
> Can anyone help?
> Thanks

execution plan

Can hardware-related properties cause an execution plan to change when a
database is copied from one SQL 2000 server to another?
I.e., indexes and statistics should remain same. But I think number of
coprocessors can have impact. What about amout of RAM? Processor speed?
Type of hard drives?
Thanks
Craig
Craig Hessel wrote:
> Can hardware-related properties cause an execution plan to change
> when a database is copied from one SQL 2000 server to another?
> I.e., indexes and statistics should remain same. But I think number
> of coprocessors can have impact. What about amout of RAM? Processor
> speed? Type of hard drives?
> Thanks
> Craig
Yes. Everything can have an effect. Make sure you update all statistics
on the new server.
David Gugick
Imceda Software
www.imceda.com
|||Yes and no. The number of processors will determine the degree to which SQL
Server might be able to run your queries in parallel. However, there must
be idle logical schedulers available at the time the query runs for it to
actually go parallel, assuming its cost is enough to make it eligible for
parallelization. (That is to say, parallelism is an execution-time
decision, and not a compile-time decision.) Memory can have an impact as it
allows the query optimizer to decrease the potential IO cost of a query:
the more memory is available, the less IO is required, and the lower the
cost of the query. Other than that, types of hard drives and processor
speed have no effect on the *generation* of a query plan; only on the
efficiency at which a plan chosen by the QO can execute.
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:%23$YHPdWDFHA.1524@.TK2MSFTNGP09.phx.gbl...
> Craig Hessel wrote:
> Yes. Everything can have an effect. Make sure you update all statistics on
> the new server.
> --
> David Gugick
> Imceda Software
> www.imceda.com

execution plan

Can hardware-related properties cause an execution plan to change when a
database is copied from one SQL 2000 server to another?
I.e., indexes and statistics should remain same. But I think number of
coprocessors can have impact. What about amout of RAM? Processor speed?
Type of hard drives?
Thanks
CraigCraig Hessel wrote:
> Can hardware-related properties cause an execution plan to change
> when a database is copied from one SQL 2000 server to another?
> I.e., indexes and statistics should remain same. But I think number
> of coprocessors can have impact. What about amout of RAM? Processor
> speed? Type of hard drives?
> Thanks
> Craig
Yes. Everything can have an effect. Make sure you update all statistics
on the new server.
--
David Gugick
Imceda Software
www.imceda.com|||Yes and no. The number of processors will determine the degree to which SQL
Server might be able to run your queries in parallel. However, there must
be idle logical schedulers available at the time the query runs for it to
actually go parallel, assuming its cost is enough to make it eligible for
parallelization. (That is to say, parallelism is an execution-time
decision, and not a compile-time decision.) Memory can have an impact as it
allows the query optimizer to decrease the potential IO cost of a query:
the more memory is available, the less IO is required, and the lower the
cost of the query. Other than that, types of hard drives and processor
speed have no effect on the *generation* of a query plan; only on the
efficiency at which a plan chosen by the QO can execute.
--
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:%23$YHPdWDFHA.1524@.TK2MSFTNGP09.phx.gbl...
> Craig Hessel wrote:
>> Can hardware-related properties cause an execution plan to change
>> when a database is copied from one SQL 2000 server to another?
>> I.e., indexes and statistics should remain same. But I think number
>> of coprocessors can have impact. What about amout of RAM? Processor
>> speed? Type of hard drives?
>> Thanks
>> Craig
> Yes. Everything can have an effect. Make sure you update all statistics on
> the new server.
> --
> David Gugick
> Imceda Software
> www.imceda.com

execution plan

Can hardware-related properties cause an execution plan to change when a
database is copied from one SQL 2000 server to another?
I.e., indexes and statistics should remain same. But I think number of
coprocessors can have impact. What about amout of RAM? Processor speed?
Type of hard drives?
Thanks
CraigCraig Hessel wrote:
> Can hardware-related properties cause an execution plan to change
> when a database is copied from one SQL 2000 server to another?
> I.e., indexes and statistics should remain same. But I think number
> of coprocessors can have impact. What about amout of RAM? Processor
> speed? Type of hard drives?
> Thanks
> Craig
Yes. Everything can have an effect. Make sure you update all statistics
on the new server.
David Gugick
Imceda Software
www.imceda.com|||Yes and no. The number of processors will determine the degree to which SQL
Server might be able to run your queries in parallel. However, there must
be idle logical schedulers available at the time the query runs for it to
actually go parallel, assuming its cost is enough to make it eligible for
parallelization. (That is to say, parallelism is an execution-time
decision, and not a compile-time decision.) Memory can have an impact as it
allows the query optimizer to decrease the potential IO cost of a query:
the more memory is available, the less IO is required, and the lower the
cost of the query. Other than that, types of hard drives and processor
speed have no effect on the *generation* of a query plan; only on the
efficiency at which a plan chosen by the QO can execute.
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:%23$YHPdWDFHA.1524@.TK2MSFTNGP09.phx.gbl...
> Craig Hessel wrote:
> Yes. Everything can have an effect. Make sure you update all statistics on
> the new server.
> --
> David Gugick
> Imceda Software
> www.imceda.com