Showing posts with label snapshot. Show all posts
Showing posts with label snapshot. Show all posts

Sunday, March 11, 2012

Does Link in Subscription Point to Live or Snapshot?

This should be an easy one...

You get an email that contains a link to a report. The email was sent automatically as part of a subscription.

Does that link point to a snapshot that was taken when the report was run, or does clicking the link cause the report to re-run altogether?

Thanks,
Dan

Hello Dan,

The link will always point to the current report. For instance, if you have an email subscription that goes out at 6am daily, and today at 8am, you open the report from the link in today's and yesterday's email, they both will take you to the most current report.

As for if it will be re-run, that depends on how you have the execution on the report setup. Whether it is 'Always run this report with the most recent data' or 'Render this report from a report execution snapshot' will determine this.

Hope this helps.

Jarret

|||

Hi Jarret,

That's exactly what I needed to know.

Thanks so much!

Dan

Sunday, February 19, 2012

Documentation of snapshot isolation level in data source

Hello all,

I was wondering if there's somewhere good documentation of the semantics of isolation level in a data source in an Analysis Services project and how the different isolation levels affect the processing of Analysis Services database. I don't mean the semantics of differerent isolation levels in SQL server, those are well documented, but what the isolation level actually means in context of an Analysis Services data source.

I'm interested in using snapshot isolation level so that when processing the Analysis Services database all the data for the Analysis Services objects would be got using a snapshot of the SQL Server database. I wonder if this is possible. There's additionally the "Maximum number of connections"-property. I assume that when processing the Analysis Services multiple connections are made to SQL server and if each of those connections use snapshot isolation level, there's no guarantee the snapshots contain the same data.

My actual problem is that the data may change in the SQL server database while processing Analysis Services database. This causes Analysis Services processing failures sometimes, since a value in the database may be found in one dimension, but not in another one.

Any ideas?

r,

J

This doesn't directly answer your question, but it might be easier to support and maintain. Try setting a flag on the records in the data warehouse tables. The flag would indicate whether or not the record was available for upload into SSAS. The flag would be set to 1 (where it was currently set to 0) at the top of the run. Data entering the tables during the run would have the flag set to the default of 0. Your queries would have logic to select just those records with the flag set to 1.

Otherwise, you can follow the steps provided in this KB article to setup/configure/use snapshot isolation:

http://support.microsoft.com/kb/919160

Good luck,

Bryan