delete
-
Everyone is forgetting about the "other" problem... the excessive row sizes that arise when doing the table ALTERs for the nocheck of constraints. It means that one or more of the tables has violated the 8060 limit and you need to find those tables and repair them. You may have to make a "sister" table to get all the data you want, but leaving it like it currently is WILL cause you a serious problem sometime in the future and likely when you least need that type of problem. Fix it now while you have the chance.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
Agreed, this is important.
As Jeff says, this is potentionally a timebomb waiting to explode...
/Kenneth
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply