Re: Error 80040e14

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: M.L. (ML_at_discussions.microsoft.com)
Date: 11/25/04


Date: Thu, 25 Nov 2004 06:15:03 -0800

Hi,

Ok?! Interesting.. Well, I am looking in the right place then? (Data File
tab in EM)

Should I manually allocate a large portion of space then? Would that be a
solution?

Thanks!

Regards,

M.L.

"Tibor Karaszi" wrote:

> There are circumstances where autogrow doesn't seem to grow fast enough, which mean that you still
> get the error.
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
>
> "M.L." <ML@discussions.microsoft.com> wrote in message
> news:4AAEAC7A-372D-40A7-9676-78EF18C91131@microsoft.com...
> > Hi Mike,
> >
> > Thanks for your answer! I have checked the disk, and there is plenty of
> > space left on the drive.
> >
> > In the Enterprise Manager, I can see that the database file properties
> > (right-click on db --> properties --> Data Files) already are set to
> > "Automatically grow file" and "Unlimited file growth". Was that what you
> > meant by expanding the DB? Why does the error appear when the DB apparently
> > is allowed to grow indefinetely? And what can I do?
> >
> > Thanks, your help is greatly appreciated!
> >
> > regards,
> >
> > /M.L.
> >
> >
> >
> > "Mike Epprecht (SQL MVP)" wrote:
> >
> > > Hi
> > >
> > > The error "Could not allocate space for object
> > > '_cc_SkuDump' in database 'CDS' because the 'PRIMARY' filegroup is full.) "
> > > indicates that your database CDS does not have enough space left to continue
> > > the Insert.
> > >
> > > Expand the database though Enteprise Manager.
> > >
> > > Regards
> > >
> > > "M.L." wrote:
> > >
> > > > Hi NG,
> > > >
> > > > I hope very much someone can help me or at least point me in the right
> > > > direction here. I have a simple Stored Procedure and all it does is it adds 4
> > > > different indexes to a rather large table which is built daily. It has been
> > > > running for 6 months now without problems, but today I found this error
> > > > message in the log:
> > > >
> > > > ---- error message from log-file-------begin
> > > >
> > > > Step 'DTSStep_DTSExecuteSQLTask_1' failed
> > > >
> > > > Step Error Source: Microsoft OLE DB Provider for SQL Server
> > > > Step Error Description:The statement has been terminated. (Microsoft OLE DB
> > > > Provider for SQL Server (80040e14): Could not allocate space for object
> > > > '_cc_SkuDump' in database 'CDS' because the 'PRIMARY' filegroup is full.)
> > > > (Microsoft OLE DB Provider for SQL Server (80040e14): Warning! The maximum
> > > > key length is 900 bytes. The index 'cluster_SkuDump' has maximum length of
> > > > 2765 bytes. For some combination of large values, the insert/update operation
> > > > will fail.)
> > > > Step Error code: 80040E14
> > > > Step Error Help File:
> > > > Step Error Help Context ID:0
> > > >
> > > > ---- error message from log-file-------end
> > > >
> > > > So what is wrong and how can I remedy it? Thanks a lot in advance!
> > > >
> > > > /M.L.
>
>
>



Relevant Pages

  • Re: Error 80040e14
    ... I suppose the problem is that the autogrow function ... > Tibor Karaszi, SQL Server MVP ... >> Should I manually allocate a large portion of space then? ... >> Regards, ...
    (microsoft.public.sqlserver.programming)
  • Re: Maintenance Plan
    ... > i shrink the data file from 30Gb to 15GB ... >> rebuilds are logged to the transaction log. ... >> Tibor Karaszi, SQL Server MVP ...
    (microsoft.public.sqlserver.server)
  • RE: Validating Decimal Values
    ... Regards ... I am having a small program which parses data file. ... also 3..00 should be marked invalid. ...
    (perl.beginners)
  • Re: Calculate the minimum and maximum data with Gnuplot
    ... An other possibility imho would be to fit the data and calculate the ... a data file. ... set term postscript eps color ...
    (comp.graphics.apps.gnuplot)
  • Re: How to make your SQL Server database grow exponentially with linear data
    ... Regards, ... Turns out it's a bug in SQL ... >> the blobs in the data file to a new data file without having to take the ...
    (microsoft.public.sqlserver.server)