Advertisement

04.27.2008 at 03:11PM PDT, ID: 23357434
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.2

Could not allocate space because primary filegroup is full error

Asked by barnesco in SQL Server 2005

When I attempt to optimize a database, I keep receiving the below error message in my error logs despite that I've shrink the data and log files:

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1105: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'AUDIT_LOG' in database 'MOEDMS' because the 'PRIMARY' filegroup is full.

The primary data file size is 99mb of 150mb allocated. The log file size is 29mb of 200mb allocated. The file sizes are restricted. This is not by choice, but what the customer wants.

The code I used to shrink the log and data files is below with the results in the attachment. The first result is the log file.

USE MASTER
BACKUP LOG MOEDMS WITH TRUNCATE_ONLY
GO
USE MOEDMS
DBCC SHRINKFILE (MOEDMS_Log, 1)
GO
USE MOEDMS
DBCC SHRINKFILE (MOEDMS, 1)
GO

Why am I receiving this error and how can I fix? Thanks.Start Free Trial
Attachments:
 
Results of file after shrinkage
Results of file after shrinkage
 
[+][-]04.27.2008 at 07:21PM PDT, ID: 21451202

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: SQL Server 2005
Sign Up Now!
Solution Provided By: paulop1975
Participating Experts: 1
Solution Grade: A
 
 
[+][-]04.27.2008 at 08:50PM PDT, ID: 21451500

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628