April 7, 2004 at 9:13 am
Hi,
Hope somebody can help me with this, have a database here which at first indexing started to fail because it complained that the primary group was full.
logged into enterprise manager and checked the diskspace. There was and is enough space on disk (database is about 4 GB and there is 13 GB free)
Then thought well, can I increase data file size, as a workaround.. but trying so I get the error: Error 5149: Modify File encountered a operatin system error 112 (there is not enough space in the disk)
Automatically file grow is on, data recovory is set to simple and I should have all the access rights to do this.
So have anybody seen this before??
Thanks for your help
Danny van Kent
April 7, 2004 at 10:06 am
I have had a problem in the past where an application needed to expand the database file (as it was full). The database started expanding, it application connection timed out. Hence sql server rolled back the expand. The application tried again, the database started expanding, the app timed out.....etc.
The problem was that the time taken to expand the database by 10% (the default) was too long. Hence lowering this percentage fixed the problem as the database expanded in the correct time span.
Ideally the database should be monitored so expansions can take place out of hours as such.
Hope this helps.
Steven
April 8, 2004 at 3:33 am
Thanks for you reply, checked it, but it's not a timeout. get the message within the second. also found out the on a other server (same settings, O/S? and hardware) I have the same... they run on Windows 2000.
Thnks anyway
Danny
April 8, 2004 at 5:22 am
Just an update, found the cause...was pretty basic :-(( The filesystem is Fat32... thus... max filesize 4GB....
Thnks
Danny
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply