DB Does Not Autogrow
Jul 24, 2007
Good Morning,
I am having a problem where I have a process that seems to fill up the database but the database does not seem to grow like it should. The database is set to autogrow by 10%... the database is around 15-16GB and it is right over 16GB when it fails. This happens once a week lately. nothing on the server has changed.
the strange thing is when you look at the database properties through EM it shows as no space available but when you do a shrink file and look at the log and data files there are over almost 2GB free on the data file and 1GB free on the log... it does no make sense...
in order for EM to show there is free space I have to add over 5GB to the data file and 1.5 GB to the log file. then processes continue...
is there something that I am missing??
View 6 Replies
Feb 27, 2000
I have a database that was autogrowing fine and now has stopped. I'm using MS SQL 7 and the database in question just reaced 32 gigabytes in size. That is the old db size limit but now it's 32 terabytes I thought. Has anybody heard of this ? Any ideas?
View 2 Replies
View Related
Oct 31, 2000
Is there a way that I can get SQL Server to tell me (Alert?) when it has grabbed another chunk of space for a database that has the "Automatically grow file" option set?
View 1 Replies
View Related
Apr 21, 2008
Hi,
I've been looking over quite a few of the sql server installations at my new job and I have been noticing that most of them are set up to autogrow the data-files by 1MB unlimited and the log-files by 10% unlimited which is the default settings when creating a new database in SSMS. This is regardless of the database size which in some cases are 400+ GB. I've usually set autogrow to a fixed MB value of around 20% of the current size, but autogrowing a 400GB database by 20% will take a considerable amount of time and could be a killer during peak hours. What would you guys recomend...?
--
Lumbago
View 2 Replies
View Related
Oct 1, 2005
Hello Folks,Last evening, as a result of our autogrow settings, our productiondatabase grew from 102 GB to 107 GB. What puzzled me is that, prior tothe growth, we still had a good 10% free space left in the data file.My understanding is that SQL Server will automatically grow a databasewhen worker thread decides that more space is necessary to fulfill arequest. We don't suspect the app of sending over a request whichwould require that much more space.Any ideas on why the file grew unexpectedly?Thanks,Joe
View 1 Replies
View Related
Jan 30, 2007
i had a problem with a server instance where an app processing a file and putting the data into the database using a stored procedure was timing out. the app is a service and in the case of errors, will try to process the file until it has been succesfully added data to the database. in the event viewer i keep seeing this message during this timeout period:
"Autogrow of file 'mydatabase_log' in database 'mydatabase' was cancelled by user or timed out after 15687 milliseconds. Use ALTER DATABASE to set a smaller FILEGROWTH value for this file or to explicitly set a new file size."
is there a possibility that this process was causing my SP to timeout? are there any other log or debug files that SQL Express creates that might be helpful in discovering what caused the timeout? currently the log is at... ouch 10gigs restricted... maybe trying to autogrow from this while restricted is hogging resources?
View 9 Replies
View Related
Dec 11, 2007
I'm currently running the command below and getting this error message. I am getting it every few seconds for a couple hours now. Seems to have started when I started this SPROC below. I'm just over 2 hours into running.
Not sure what this means yet, any help is much appreciated. Desperately trying to resolve this urgent matter!
thanks once again!
mike123
"Autogrow of file 'templog' in database 'tempdb' was cancelled by user or timed out after 2813 milliseconds. Use ALTER DATABASE to set a smaller FILEGROWTH value for this file or to explicitly set a new file size."
EXEC isp_ALTER_INDEX
@dbName = 'db1',
@statsMode = 'DETAILED',
@defragType = 'REBUILD',
@minFragPercent = 10,
@maxFragPercent = 100,
@minRowCount = 1000
View 4 Replies
View Related
May 27, 2008
We are running Microsoft SQL 2005 Express.
All queries on our Production database are timing out. Viewing the error log file the following show up over and over again:
Autogrow of file 'tempdev' in database 'tempdb' was cancelled by user or timed out after 3937 milliseconds. Use ALTER DATABASE to set a smaller FILEGROWTH value for this file or to explicitly set a new file size.
Autogrow of file 'Prod' in database 'Production' was cancelled by user or timed out after 33156 milliseconds. Use ALTER DATABASE to set a smaller FILEGROWTH value for this file or to explicitly set a new file size.
Our production database is about 1 gig in size with 3.5 million records. I tried setting the autogrow from 30% which it was before to 100MB, but no luck, still timing out and getting the errors above. Permission should be all good, nothing has changed.
There is about 50gigs of available disk space as well, so that's not the problem. Thanks for the help.
View 51 Replies
View Related
Jun 26, 2007
Afternoon
I'm getting the below error message:
Autogrow of file 'FORMS' in database 'FORMS' cancelled or timed out after 30547 ms. Use ALTER DATABASE to set a smaller FILEGROWTH or to set a new size.
FORMS.LDF file is 7613952 KBand the growth is 512MB .
By how much should I set the filegrowth? The users are complaining that the application is freezing on them.
This is sqlserver 2000.
View 6 Replies
View Related
