Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2005-07-08 : 07:13:55
|
| Jason Adams writes "I have a stored proc that has worked fine for several weeks. One of the things that the SP does is an update and an insert to a table. I recently added an indexed view to this table. The stored proc now fails intermittently (Server: Msg 8624 … Internal SQL Server error) during either the update or the insert statement for this table. If I drop the index on the view the stored proc works again without fail.During some debugging I noticed that even generating an execution plan (<CTRL>-L) under the right data conditions cause the Internal SQL Server error. One of the suggestions I found when researching this problem was to not allow the query to go parallel. I tried this in my debugging session using the OPTION(MAXDOP 1) for both the insert and the update queries and found that without the option the query failed and with the option the query worked.I implemented the OPTION(MAXDOP 1) option and found that the error condition still occurs. The SP worked for some of the update/inserts but when it got to a larger result set it failed again with the same Internal SQL Server error.My only solution at the moment is to drop the index do the update/inserts and re-create the index. This is really not an acceptable long term solution.Any help or suggestions would be great. We are currently on SQL Server 2000 SP3A on a Windows 2003 Server." |
|
|
madhivanan
Premature Yak Congratulator
22864 Posts |
|
|
|
|
|