Hi,
this week, i had to drop a column from a table (table has 40 columns, 3600 rows). So nothing special eh? No big table in size or rows, but the table is referenced in more than 400 objects (stored procedures, triggers, views, SQL Functions). These objects are constantly used by our users...
Dropping the column is very fast, but the transaction log grows almost instantly about 400MB (normally, on this system the transaction log grows about 150MB / hour). We have 1024MB configured and for the next half hour, the log increases faster than normal (our full database dump takes about 50 minutes, so thats a long time too see our transaction log growing fast closing in to 1024MB)
Why is this? Are all objects that reference this table recompiled perhaps? And why does this affect our transaction log?
And maybe the most important question, what can we do about it?
ps: i know i can increase our transaction log, but thats not the issue right now...
Greetz
Pieter
Adaptive Server Enterprise/15.7/EBF 21985 SMP SP110 /P/X64/Windows Server/ase157sp11x/3546/64-bit/OPT/Fri Nov 08 01:38:31 2013