Basic Functionality Questions

We've been trying to implement Reporting Services in our web application. We've run into 2 issues that I'd like to verify:

First, HTML rendering. In our application we provide an HTML Editor for formatting. The formatting does not render in the reporting services. I understand that's a known issue with no work around and no timeframe for resolution. Is that correct?

Second issue comes with tying is the Reporting Services together with our ASP.NET code. Do any of the Reporting Services controls allow you to bind to classes that support the IList Interface?

Thanks,

Frank

1) RS text box control does not render HTML. It supports standard formatting which applies to the entire contents of the textbox rather than individual bits of text as in a rich text box control.

2) RS reports are rendered based on the report definition and do not support binding custom datasets at runtime through the IList interface.

sql

Base Functionality Script

Hello, everyone:
In the BOL about Designing a Backup and Restore Strategy, it is mentioned there is a Base Functionality Script that should be run after SQL Server restored. What is Base Functionality Script? Just DBCC CHECKDB? Anything else?
Thanks
ZYTA "base functionality script" is a batch of code that can be used to quickly demonstrate the successful functioning of the database from a specific application's perspective. Most commonly this is a .sql file with batched SQL commands run into the server from ISQL. For other applications, a .bat file is more appropriate because it can contain BCP and ISQL commands. This base functionality script is very application-specific, and can take many different forms. For example, on a Decision Support/Reporting system, the script may merely be a copy of a couple of your key reporting queries; for an online transaction processing (OLTP) application it may be the execution of a batch of stored procedures to execute INSERT, UPDATE, and DELETE statements. The goal is to confirm, from a gross perspective, that everything is working as intended. The base functionality script provides a nice tool for the SA or DBA to be able to see that the database is back in a viable state, without depending on the end users for verification.