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 |
|
Wrangler
Starting Member
35 Posts |
 Posted - 2011-11-23 : 13:25:23
|
| I'm getting a full filegroup alert 17 on a drive with 42GB free space while trying to run an update statement. The table is 61GB. The update statement updates 2 columns: varchar(11) and varchar(9). The 2 columns being updated are not in the clustered index. The number of rows affected is by the update is 13 million. error:Could not allocate space for object 'dbo.ClaimD'.'PK_ClaimD' in database 'XXXX' because the 'IX_FG1' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.Any ideas?Thank you |
|
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2011-11-23 : 13:33:26
|
| It's failing on updating PK_ClaimD which sounds like a primary key - is it clustered. Is there a max size for the files?If you are updating those columns to be larger then it could cause a lot of page splitting and general moving of data.Why not do it in batches.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
Wrangler
Starting Member
35 Posts |
Posted - 2011-11-23 : 13:47:05
|
| Found the issue. The files are restricted to 30GB and all are full. I created another file in the filegroup. Doh. Should have checked that first. Thanks. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
full filegroup
Tara Kizer