Performance Gains using Indexed Views and Computed Columns

Hello

This is a quick follow-up blog to the Presention I gave last night @ the London UG Meeting ( 17th March 2010 )

It was a great evening and we had a big full house (over 120 Registered for this event), due to time constraints we had I was unable to spend enough time on this topic to really give it justice or any the myriad of questions that arose form the session, I will be gathering all my material and putting a comprehensive BLOG entry on this topic in the next couple of days..

In the meantime here is the slides from last night if you wanted to again review it or if you where not @ the meeting

If you wish to contact me then please feel free to send me emails @ Neil.Hambly@hotmail.co.uk

Finally  - a quick thanks to Tony Rogerson for allowing me to be a Presenter last night (so we know who we can blame !)  and all the other presenters for thier support

Watch this space Folks more to follow soon.. 

 

Published 18 March 2010 10:41 by NeilHambly
Filed under: ,

Comments

18 March 2010 11:38 by jamiet

# re: Performance Gains using Indexed Views and Computed Columns

Thanks for the presentation last night Neil, really useful stuff.

21 March 2010 14:52 by NeilHambly

# re: Performance Gains using Indexed Views and Computed Columns

You receive an incorrect result when you enable the ANSI_NULLS database option and run a query against an indexed view in SQL Server 2005 or in SQL Server 2008

Article ID: 967983 - support.microsoft.com/.../967983

Try to make sure you have the most recent CU / Fixes available on your system to resolve or prevent these type of issues.

23 March 2010 18:49 by Calendar spread on News Corp. | JSP WebDev Insider

# Calendar spread on News Corp. | JSP WebDev Insider

Pingback from  Calendar spread on News Corp. | JSP WebDev Insider

24 March 2010 02:54 by jamesl

# re: Performance Gains using Indexed Views and Computed Columns

Hi Neil,

I read the slides with interest. I would like to ask a question.

I work for a company who currently has a legacy system with data replicated between remote database within the same local domain.

We are looking at removing this replication and replacing the locally replicated tables with remote views. The full replication of data was always overkill for our solution and creates excessive administrative overheads.

What are the implications of the views being of a table on a remote database. Is it indeed possible to have Indexed views on remote databases?

Are remote views a good idea; in your experience?

thanks

J

24 March 2010 12:09 by NeilHambly

# re: Performance Gains using Indexed Views and Computed Columns

James

Has raise a good question on use of indexed views

(note: my blog explaining this and more is nearly done and will be posted very soon)

But to answer this question some:

Indexed Views CAN ONLY be on Tables (in the same database), however you can still query these views remotely and perform any joins with other tables  /views

Again just think of the indexed view as a table, so querying from another database (I.E As a remote table) you would employ the an same appropriate access strategy: use of Openquery/rowset, linked servers etc..

Replicating data is used in mostly in scenarios where Availaibilty & performance considerations outweigh the overhead, classic examples are replication / log shipping relevant data to a reporting / DW staging DB system - these generally have much different workloads to an OLTP.. I.E They can reuire very different indexing strategies