Welcome to MSDN Blogs Sign in | Join | Help

August 2005 - Posts

A couple of post IDW15 changes when building Report Builder Models in SQL Server Reporting Services 2005

While playing around with newer builds of Yukon, I noticed two changes from IDW15/CTP15 when it comes to building models: (Thanks to Carolyn Chau!) Up until IDW15/CTP15, you used the IdentifyingAttributes property of an entity to specify which fields/attributes

2005 report farms and the Surface Area Configration tool. The horror! The horror!

I just spent an entertaining hour trying to get a 2005 Reporting Services web farm operational. It's up now, but I'm a tired, broken man. Here are the mistakes I made: On certain 2005 SKUs, the Remote Connection property for your database engine is set

Tuning scheduled/delivery-related processes in a SQL Server Reporting Services Reporting Farm

[Thanks to Robert Bruckner, Daniel Reib, Tudor Trufinescu and Mike Schetterer!] Using rsConfig.exe and rsActivate.exe, you can easily set up a reporting farm in which multiple instances of the Report Server web and windows service use the same ReportServer

Querying ExecutionLog in SQL Server Reporting Services: discretion is the better part of valor

I have to admit that I fairly regularly query the ReportServer..ExecutionLog table to look at the performance characteristics of my reports rather than using the RS_ExecutionLog_Update.dts package like I'm supposed to. I'm frankly lazy, and don't want

Creating Report Subscriptions via SQL Managment Studio in SQL Server 2005

Just ran into an interesting little behavior in SQL Management Studio when I tried to create a subscription on a new report: At the time, I didn't realize that I wasn't using stored credentials for the datasource the report utilizes. I went to SQL Management

SQL Server Integration Services: Sometimes BCP is "good enough".

Today I sat in on a SSIS performance tuning "chalk talk" given by Ashvini Sharma at TechReady, an internal technical education event. Ashvini mentioned that when loading relatively small amounts of data into SQL (he characterized small as < 1 GB),

Forms authentication and the ReportingService Web Service

After you've gotten the SQL Reporting Services Forms Authentication sample working, the next logical thing to do is access the Web Service itself while your SSRS instance is running under forms auth...but how do you authenticate? Rather than populating
 
Page view tracker