sql server programming: problem creating indexes on large tables -- sql server programming

Re: problem creating indexes on large tables

Andrew J. Kelly
10/7/2004 7:44:54 PM

sql server programming: The error message does not reference the log file at all. It refers to the
Primary Filegroup which is where your data file(s) live. You either don't
have enough room on the disk where the Primary files live or the files can
not autogrow fast enough. First off turn off Auto Shrink as it is causing
more problems than it will fix. Then manually expand your file(s) in your
primary filegroup to a size larger than you need to hold all the data and
indexes in the database. Then try creating your indexes.

--
Andrew J. Kelly SQL MVP

[quoted text, click to view]

problem creating indexes on large tables

PeyoQuintero
10/7/2004 11:31:15 PM

Hi there,

I have a SP that create some indexes on large tables. When the tables have a
lot of data, I get this sql server error:

"Could not allocate space for object 'Import_FDSTAT' in database 'AS400CAD'
because the 'PRIMARY' filegroup is full."
The database is configured in SIMPLE mode, with auto-shrink, and the
transaction log is configured to grow automatically, so it shouldn'r run out
of space.

Also, after running each 'CREATE INDEX' command I am running this
statement

backup log dbname WITH NO_LOG

I still get the error message.

I really need help on this one, I can't figure out what is going on.

Thanks.

Peter.