jamminjaymeyer
Programmer
I have disk space available and I have the auto grow set to grow 10 % and unlimited growth but it still will not grow and says my primary file group is full. Any ideas?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
DB Will Not Grow 1
- Thread starter jamminjaymeyer
- Start date
- Status
Is 10% of your existing size exceeds the available space? Set the parameter in MB, not in %. This is one of my pet peeves: setting autogrow in % is dangerous if you have 10GB database and set increase 10% - it means 1GB will be allocated and reserved even if you need only couple more KB...
- Thread starter
- #3
jamminjaymeyer
Programmer
MY Db is less than a gig and I have 10 gig avail. I did try to do it by MB also but it won't work that way either.
I tried to set the space allocated to the datta file up but that would not save my change.
Anyone had this same problem?
I tried to set the space allocated to the datta file up but that would not save my change.
Anyone had this same problem?
-
1
- #4
tlbroadbent
MIS
What query or activity is causing the error message to occur?
If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
- Thread starter
- #5
jamminjaymeyer
Programmer
I have a DTS package that is copying records from another table on the same server no fancy transformations or anything, just a straight copy. It works fine up unitl it runs out of space and then says it is out of room and stops the DTS package.
- Thread starter
- #6
jamminjaymeyer
Programmer
Another funny update to this problem is that the Transaction log is also set to grow and it grows fine, it is just the DB file that will not grow.
Anyone had this problem?
Anyone had this problem?
- Thread starter
- #7
jamminjaymeyer
Programmer
I also get this error in the SQL Logs:
fcb::ZeroFile(): GetOverLappedResult() failed with error 2.
fcb::ZeroFile(): GetOverLappedResult() failed with error 2.
tlbroadbent
MIS
I'm not familiar with the SQL Error Log message. I assume it occurs at the same time as the "primary file group is full" message. My feeling is that the file full message may cause the other error message but I'm not sure. Is there additional information provided with the "GetOverLappedResult() failed" message?
"I tried to set the space allocated to the datta file up but that would not save my change."
What happens when you try to preallocate more space to the database? Do you get an error message? If so what is it.
We occasionally see the "file group full" or "transaction log full" messages when there is sufficient space and the files are set to grow with no upper size limit. We've come to the conclusion that there are times, especially when performing bulk inserts, that SQL Server cannot grow the file(s) fast enough and thus the file full messages are generated. In these cases we set the growth factor in MB rather than percent and increase the file size before starting the bulk-load process as you've apparently tried to do. I think you need to determine why you cannot set the file size larger.
Which version of SQL Server are you running? What is the latest service pack installed?
If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
"I tried to set the space allocated to the datta file up but that would not save my change."
What happens when you try to preallocate more space to the database? Do you get an error message? If so what is it.
We occasionally see the "file group full" or "transaction log full" messages when there is sufficient space and the files are set to grow with no upper size limit. We've come to the conclusion that there are times, especially when performing bulk inserts, that SQL Server cannot grow the file(s) fast enough and thus the file full messages are generated. In these cases we set the growth factor in MB rather than percent and increase the file size before starting the bulk-load process as you've apparently tried to do. I think you need to determine why you cannot set the file size larger.
Which version of SQL Server are you running? What is the latest service pack installed?
If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
- Thread starter
- #9
jamminjaymeyer
Programmer
Thank you for the reply.
I am running SQL Server 2000 with SP3 and all avail hotfixes and security patches since then. I try to keep very current on patches and security hotfixes. It is on a rather large IBM Win 2K server box with all the latest SP and security hotfixes.
I have read the problem when the file can not grow fast enough to keep up and I agree with you that does not seem to be the problem. If that was the case I should still be able to grow the file manually with Enterprise manager or Alter Database command. When I try to change the file size in Enterprise manager it acts like it changes it but if I change it press OK then open it back up it is set back to what it was previously, and puts the following error in the SQL error logs:
Source spid65
fcb::ZeroFile(): GetOverLappedResult() failed with error 2.
The same error happens in the SQL error logs when running the Alter Database command even though it says it completed successfully it never changes the size.
I do think this error is the source of my problem but I can find it no where on the web, on Microsoft’s site, in this or any other message boards even. Either I have something set up very wrong or I found a new bug.
The real thing that gets me is that the transaction log grows just fine but the data file will not. Although if I try to shrink the transaction log file it will not shrink, which maybe related to this or it could be it’s own problem.
I have tried to set it to grow in MB rather than % I agree this should be the way it is always don, but that does not seem to help either.
I am running SQL Server 2000 with SP3 and all avail hotfixes and security patches since then. I try to keep very current on patches and security hotfixes. It is on a rather large IBM Win 2K server box with all the latest SP and security hotfixes.
I have read the problem when the file can not grow fast enough to keep up and I agree with you that does not seem to be the problem. If that was the case I should still be able to grow the file manually with Enterprise manager or Alter Database command. When I try to change the file size in Enterprise manager it acts like it changes it but if I change it press OK then open it back up it is set back to what it was previously, and puts the following error in the SQL error logs:
Source spid65
fcb::ZeroFile(): GetOverLappedResult() failed with error 2.
The same error happens in the SQL error logs when running the Alter Database command even though it says it completed successfully it never changes the size.
I do think this error is the source of my problem but I can find it no where on the web, on Microsoft’s site, in this or any other message boards even. Either I have something set up very wrong or I found a new bug.
The real thing that gets me is that the transaction log grows just fine but the data file will not. Although if I try to shrink the transaction log file it will not shrink, which maybe related to this or it could be it’s own problem.
I have tried to set it to grow in MB rather than % I agree this should be the way it is always don, but that does not seem to help either.
tlbroadbent
MIS
GetOverLappedResult appears to stem from an OS error. Is it possible that the server administrator has setup disk quotas on the server, limiting the amount of disk space available to the SQL Server account?
If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
- Thread starter
- #11
jamminjaymeyer
Programmer
Well I am the administrator and I am not sure how to even do that. I wonder if it is something I set by mistake. Anyone know how to check this?
tlbroadbent
MIS
I don't know how but Microsoft does. Check the following.
How to Enable Disk Quotas in Windows 2000
If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
How to Enable Disk Quotas in Windows 2000
If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
I have seen a simmilar issue in SQL 7.
The fix for me was I needed to make the SQLCMDexec user an admin on the local machine.
Check to see that the SQLCMDexec user has the permissions on the local machine to the HD. IF not then you will get a similar issue (or passwords expired).
The fix for me was I needed to make the SQLCMDexec user an admin on the local machine.
Check to see that the SQLCMDexec user has the permissions on the local machine to the HD. IF not then you will get a similar issue (or passwords expired).
- Thread starter
- #14
jamminjaymeyer
Programmer
Well I checked and I do not have any disk quota's set and I do not have a user called SQLCMDexec on the server but the accounts I do have are full admin rights. Is there an easy way to report something like this to Microsoft?
tlbroadbent
MIS
You can contact Microsoft Professional Support Services. Click the following link to open a page listing various support options.
If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question