Data validation for datetime parameter in SSRS.
Came across this piece of code for ensuring the end date comes after the start date. Just what I was about to write but a quick Google search saved a bit of time. Yay! Read the rest of this entry »
Popularity: 15% [?]
A use case has been presented where users wish to receive email notification of certain records matching various criteria. Additionally, the notification subscription should only notify the user if records exist matching the criteria. The notification via subscriptions should only happen once for any given record. Read the rest of this entry »
Popularity: 21% [?]
While working with time series charts in SQL Server Reporting Services, I ran across a particular need to show cumulative aggregation of income over time by fiscal year. Yup, that’s a mouthful eh? I initially thought great, I’ll just make the Y-axis value be the running total of the !Fields:Total.Value for the fiscal year series grouping using the RunningValue() function. This worked great with the exception of the current fiscal year. Read the rest of this entry »
Popularity: 34% [?]
Are you new to SQL Server Reporting Services? Want to know some more before investing too much in additional training? Just plain curious?
Below is a list of some of the better video tutorials we’ve found on the web.
Popularity: 57% [?]
The MSDN Webcast from September 8, 2008 is the third in a series entitled “SQL Server 2008 Tips & Tricks” focuses on Reporting Services 2008.
Presentation and slide content by IT Mentors
1. SSRS 2008 Architecture/Runtime
2. Configuration
3. New Controls
a. Tablix
b. Gauges and Indicators
4. Deployment
### Benefits of Eliminating IIS from the SSRS Architecture
* Easier configuration
* IIS settings for other applications impact SSRS
* Better resource management
* IIS designed for static or dynamic HTML pages, not report execution for large reports to many concurrent users.
* Memory management easier to implement outside of IIS
* Consolidation of two services into one
* Communication process between services eliminated
* More efficient allocation of memory across server
* Elimination of deployment obstacles
* SQL Server DBAs lacking IIS skills
* IT policies prevent IIS and SQL Server on same server
### Architecture
* HTTP Listener
* Uses HTTP.SYS directly from the operating system
* Accepts requests directed to the configured URL and port
* Authentication Layer
* Confirms identity associated with request
* Supports Windows, Basic, or anonymous Access with a custom authentication
* Application Domains
* Provide a front-end component with Report Manager
* Process reports interactively with Report Server Web service
* Support scheduled operations with background processing
* Application Domain Management
* Replaces IIS functionality
Notes: Speaker does not discuss the complications that running IIS and SSRS 2008 on the same server. Instead he talks about how they both can run on the same server. Might want to be sure you understand the complications that can arise from both on the same server, especially when it comes to SSL needs.
### Configuration
* Memory Management
* Disabling Features
Notes: Speaker states the obvious about the importance of these items. Disabling features = reducing surface area.
### Memory Management
* Memory Broker monitors and responds to memory pressure fluctuations
* Memory events trigger switch from RAM to file system cache as needed
* Configurable thresholds determine report server response to memory pressure changes
Notes: Good simplistic explanation of these by the speaker. Might want to research a bit more if you really need to tweak memory optimization for peak performance.
* Low Memory Pressure
* Current requests continue
* New Requests accepted
* Background low priority
* Medium Memory Pressure
* Current requests continue
* New requests _might_ be accepted
* Memory allocations reduced for all applications
* Background items get the largest reduction
* High Memory Pressure
* Current requests continue
* No new requests accepted
Notes: Good explanation and slide for this concept.
### Configure Memory Settings
Notes: Speaker shows you the what to change in the config file but neglects to say which config files is being changed and where it is located. The correlating MSDN article on this topic is located here.
Information on the RSReportServer.config file can also be found on MSDN.
### Disabling Features
* Report Manager
* RSReportServer.config
* IsReportManagerEnabled
* On Demand Processing
* RSReportServer.config
* IsWebServiceEnabled
* Scheduled Events and Report Delivery
* RSReportServer.config
* IsSchedulingService
* IsNotificationService
* IsEventService
* Report Builder
* SQL Server Management Studio
* Server Properties
* Report Server Windows Service
* SQL Server Configuration Manager
Notes: One might want to consider the “Why?” on each of these to determine appropriate use cases for enabling or disabling. Now the speaker shows where the config file is.
Demos were done for memory configuration settings and the Tablix control.
Lots of good gauges and indicators available thanks to the new Dundas obtained controls.
Finally discussion about the rs command line tool for deployment.
Popularity: 43% [?]
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% [?]
