Wrox Programmer Forums
Go Back   Wrox Programmer Forums > SQL Server > SQL Server 2000 > SQL Server 2000
|
SQL Server 2000 General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old November 2nd, 2006, 06:05 PM
Friend of Wrox
 
Join Date: Oct 2006
Posts: 112
Thanks: 12
Thanked 0 Times in 0 Posts
Default "PRIMARY" filegroup is full...

Hi all,

I'm gotting this error message...

"Could not allocate space for object 'SY03400' in database 'NAME'
because 'PRIMARY' filegroup is full"

How can I resolve this...

Thanking in advance
Rino

 
Old November 2nd, 2006, 10:42 PM
Friend of Wrox
 
Join Date: Oct 2006
Posts: 475
Thanks: 0
Thanked 9 Times in 9 Posts
Default

You need to look at the drive that the Primary file group is on... physically, it is full. You either need to remove something from it or make a secondary file group on another drive. You may be able to recover some space if your log is on the same drive by doing a backup to decrease the space used and then shrink the log. Then, perhaps, move the log to another drive which will also have the benefit of increasing performance on the server overall.

--Jeff Moden
 
Old November 3rd, 2006, 12:51 PM
Friend of Wrox
 
Join Date: Oct 2006
Posts: 112
Thanks: 12
Thanked 0 Times in 0 Posts
Default

I shinked the log and it did free up space...
By moving the log to another drive would that case problem to database in anyway...

One other question...
Would I get the same error message if on the server there is a bad sector on one of the drivers... That when SQL trying to write to it it can't...



 
Old November 3rd, 2006, 08:10 PM
Friend of Wrox
 
Join Date: Oct 2006
Posts: 475
Thanks: 0
Thanked 9 Times in 9 Posts
Default

[u]Properly</u> moving the log file to another drive will only do one thing... increase performance of the server.

I suppose it is possible if you have a sector that went bad AFTER the disk space was allocated after use. It shouldn't matter before hand because SQL Server will not allocate to a known bad sector. Perhaps a run of SCANDISK from the command prompt would be appropriate to find out...

Make SURE you have a full backup of the database before you try to move the log file OR do SCANDISK.

--Jeff Moden





Similar Threads
Thread Thread Starter Forum Replies Last Post
FULL of ERRORS slme BOOK: Beginning ASP.NET 2.0 BOOK VB ISBN: 978-0-7645-8850-1; C# ISBN: 978-0-470-04258-8 1 May 4th, 2008 03:47 PM
Tempdb is full koushikroy2001 SQL Server 2000 0 August 5th, 2005 05:42 AM
Full On PHP Help Drip Beginning PHP 1 September 25th, 2004 11:29 AM
Full Screen surendran Flash (all versions) 1 August 3rd, 2004 07:41 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.