1

I have a view that I'd like to apply a full text index on. It of course needs a unique clustered index to allow for the full text index.

Unforunately, I learned that you cannot create an indexed view that contains outer joins. Problem is that my view needs these outer joins!

Is there a way to make this happen, or am I going to be stuck writing a complex stored procedure?

ScottE
  • 21,530
  • 18
  • 94
  • 131
  • Just a suggestion outside the context of your question...take a look at Lucene.NET. This will provide you speedier query times along with more flexible querying capabilities. I think they also have a plugin that can sit on top of your SQL Server database so that you don't have to create and maintain external indexes. This has saved our but on several instances in my current project. SQL Server just can't compare! – Andrew Siemer Jul 07 '09 at 20:42
  • @Andew - Do you have a link to this plugin? – jjxtra Jul 07 '09 at 21:07
  • Try here for an intro: http://www.codeproject.com/KB/library/IntroducingLucene.aspx – ScottE Jul 08 '09 at 01:59

1 Answers1

0

Is it possible to create a dummy record to join to for the purposes of this view?

Antony
  • 3,781
  • 1
  • 25
  • 32
  • Yes, that would definitely work. It would require some work to re-architect, but is probably the only solution for indexing the view. I'll mark you as correct, but I did end up going the stored procedure route, which turned out to be not so bad! – ScottE Jul 10 '09 at 11:11