January 3, 2002 at 11:02 pm
Hi all
This is a very general Q, but ive noticed a number of times that a schema change (ie. new column on a table etc) will cause stored procedures that have a cursor open to crash a burn with an error related to the schema being changes whilst the cursor was open. This occurs even when the cursor is NOT touching any of the tables that were altered. Strangely enough it doesnt extend to altering stored procs and views.
Thoughts on this? ie.
a) was this typically behavior in previous versions (prior to v7)
b) any reason why this happens?? as I cant think of a good reason
Cheers
Chris
Chris Kempster
www.chriskempster.com
Author of "SQL Server Backup, Recovery & Troubleshooting"
Author of "SQL Server 2k for the Oracle DBA"
January 4, 2002 at 4:42 am
You wouldnt think it would happen, schema locks would seem to be there to prevent this. I know I've seen errors occur when modifying an index live - a pain!
Andy
January 4, 2002 at 10:20 am
Never seen this, but we tend to make these mods when everyone is locked out. We also script do that the changes occur in a minimal amount of time.
Steve Jones
January 4, 2002 at 10:20 am
Never seen this, but we tend to make these mods when everyone is locked out. We also script do that the changes occur in a minimal amount of time.
Steve Jones
January 4, 2002 at 12:34 pm
Maybe it's an issue because of changes being made to system tables? Though one would think Microsoft would have ensured this wouldn't have been an issue. Hrm. I'm going to have to play with this in a test environment.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply