We just ordered our licenses for SQL Server 2008 (various editions). 
Now it is time to get ready for the migration. While doing some research on the actual report .rdl upgrade process I figured I’d put my findings here.
The Performance Point Blog has this FAQ that has a few good tidbits. The one that stuck out to me was the last one:
“Q: I know that every once in a while, a 2005 report won’t auto-upgrade to
2008 successfully. How can I tell if a report I’m running is being rendered in 2005 or 2008 mode?
A: We attempt to upgrade a 2005 report to 2008 once and only once. If the process fails the first time, we don’t try again. To see which engine is being used to render a report, use the new ExecutionLog2 view in the
reportserver database, examine the AdditionalInfo column and check the <ProcessingEngine> element. A value of 2 indicates the new 2008 “on demand” rendering engine was used, while a value of 1 means the older, 2005 engine was used.”
Seems like a quick way of seeing which engine is being used when you first hit those reports after upgrading the server. Good stuff.
A brief take from Cliff Nelson is here referencing an internal discussion guided by Robert Bruckner.
Oh, I have to say that I am very excited about the chart, graph and gauge controls, a la Dundas, that are included as part of SSRS 2008. Plus, there available for the .Net framework 3.5 as standalone controls. Yipee!
As we move further in this process I’ll post any important pieces here for my use and yours.
Blessings.
Popularity: 22% [?]
