|
Posted by Jason Wilson on 10/12/07 21:40
I was looking to improve the performance of an ASP.NET application by
creating the an indexed view that could be used instead of some of the
root tables.
What I didn't realize is that it would affect any future conenctions
to the root tables.
This of course crashed the application on any type of insert, update,
or delte from the root tables.
Funny thing is when I removed the indexed view -- it didn't help.
I tried flipping the offending options to the opposite of way they
were set on the database and the errors wouldn't go away.
I ended up restoring the database from before my mess up to fix it.
I was hoping that the SQL experts out there might shed some light on
my problem before I try again.
Navigation:
[Reply to this message]
|