[dba-SQLServer] Warning, the table

Francisco Tapia fhtapia at gmail.com
Fri Oct 8 11:54:16 CDT 2004


IF you add a column via EM, it may rebuild the table since it actually
re-creates the table and copies the data, and drops the old one...
(depending on where you add the column).

if you do this via QA the syntax looks like this


ALTER TABLE myVLDB ADD myClumnName INT



On Fri, 08 Oct 2004 11:50:55 -0400, John W. Colby
<jwcolby at colbyconsulting.com> wrote:
> When I try to add a field to the table it gives me a "Warning, the table was
> created with Ansi Nulls OFF.  The table will be recreated with Ansi Nulls
> ON".  I know from experience that this causes the db to go off for days at a
> time rebuilding the table.
> 
> What the <expletive deleted> are ansi nulls and why was the table created
> with it off?
> Why do I need them now?
> Is there any way to prevent this and yet still be able to add a field?
> Is there any way to allow setting ansi nulls on but not "rebuilding the
> table"?
> 
> I already added a field (an int identity) and it told me it was rebuilding
> the table for that field.  Why is it having to rebuild the table again.
> This is getting rather silly especially since it takes literally days to
> rebuild the table.
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> Contribute your unused CPU cycles to a good cause:
> http://folding.stanford.edu/
> 
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
> 
> 


-- 
-Francisco
<a href="http://pcthis.blogspot.com">Pc This! pc news with out the jargon</a>



More information about the dba-SQLServer mailing list