One more addition to the list http://vyaskn.tripod.com/sql_server_check_identity_columns.htm 

You can check out this whitepaper. It gives various architectural options.

Whenever there is a bug in front end reports, the first thing people assume some thing wrong with the ETL or ETL has corrupted the data :-). My advice is...

Thanks for that.

David,

Thanks for good article.

Other approach would be use the xml data type feature in SQL Server 2005 to store the XML documents.

Dave,

Yes you can place the data in another table. You can check this url for more details .

I would strongly suggest to archive the old data(may be you can write a small job which regularly archives the data to table/flat file).

The article at http://www.dbazine.com/sql/sql-articles/charran3 migh help you.

To start , this is a good tutorial.

Thanks Steve, that was good article. Some of the features i really like in SQL Server 2005 are

• CTEs.
• XML Support.
• Try catch blocks
• Online indexings.
• CLR integration.

If your application does not need any of...

Jonathan,

It is always better to query INFORMATION_SCHEMA views rather than directly quering the sytem table.

Microsoft recommends using INFORMATION_SCHEMA views.

Thanks all for your replies.

Good work Grant..

If you want to use indexed views in non enterprise editions, you can use the hint NOEXPAND. The NOEXPAND view hint forces the query optimizer to treat the view like...