Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
pmccann1
Posting Yak Master
107 Posts |
 Posted - 2006-09-18 : 04:26:54
|
| i am getting the following error and need to contact the server people but i am not sure what to get them to look atCould not allocate space for object 'test' in database 'Ark' because the 'PRIMARY' filegroup is full |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2006-09-18 : 04:31:23
|
| Most probably you are out of disk space. Try to create the database on a different disk.Peter LarssonHelsingborg, Sweden |
 |
|
|
anilkdanta
Starting Member
25 Posts |
Posted - 2006-09-18 : 05:15:20
|
| The reason you are getting this error can be 1) The Disk is full2) The database data, log file settings are not allowing the file to shrink automatically OR database size is restricted ( should be auto grow)Diagnose this problem considering the above 2 points. If the disk is full you have to look for a bigger capacity disk to move this database. |
|
|
|
EugeneZ
Starting Member
26 Posts |
Posted - 2006-09-19 : 18:03:52
|
| run transaction log backup:for example:Backup log yourdb with truncate_only--then shrink database---also if it is sql server 2k - if you do not need trans log backups change recovery mode to 'Simple' - (sql server properties)also check if size of the database file is not resticted |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-09-19 : 18:27:21
|
| pmccann1, how much disk space is available on the disk where the MDF file for database Ark is located?anilkdanta, you should never have the autoshrink option enabled for performance reasons. If you need to shrink the file, just issue the DBCC SHRINK comamnds. eugeneZ, backing up the transaction log with the truncate_only will not fix this issue as the error indicates it's a problem with the MDF file, not the LDF file. Tara Kizer |
|
|
|
anilkdanta
Starting Member
25 Posts |
Posted - 2006-09-20 : 01:25:08
|
| tkizer,Thanks for your correction. I read a article published on WWW which says autoshrink is required. Can you please let me know, why it is a performance issue even it is not done on a regular basis.ThanksAnil |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-09-20 : 10:28:48
|
| You never know when autoshrink is going to run! It does it whenever. You could be running a very important job or your users or running some critical processes that are time dependent and the autoshrink kicks in which would cause blocking. You should never have this option checked in production.Tara Kizer |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2006-09-20 : 15:16:12
|
| "I read a article published on WWW which says autoshrink is required"Its wrong.So your database grows to 100MB, say.You shrink it back to, say, 50MB.It grows to 100MB ...... you needed 100MB of disk space anyway, why waste CPU cycles on the Shrink - AND the Grow!Each Shrink/Grow is likely to fragment the files further - also reducing performance.Kristen |
|
|
|
|
|
|
|
|
space issue