Tell me more ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.
up vote 2 down vote favorite

I have a local project i am working on, on my own workstation. I use a local SQL server as well.

The project contains alot of data, and as of now, i just need to be able to store all this data in the SQL db. The main PRIMARY file is, as of now, in the size of 9,5 GB. I keept getting the error "Could not allocate space for object 'dbo.History' in database '[path to mdf]' because the 'PRIMARY' filegroup is full". I then tried fiddling with the autogrowth porperties (default was "By 10 percent, unrestricted growth". I have around 60gb free on the disk. I then tried setting it to "By 50000 mb, unrestricted growth", and adding 4 more primary files - but i still get the same error?

What can i do - i am not really to concerned about how and why the db is so large, i just want the SQL server to accomodate the size of the files.

share|improve this question
1  
Forgot to mention that i am running SQL Server Express 2008 R2. And i just found a post saying "SQL Server Express 2008 R2 is limited to 10GB.". So it looks like this could be where the error is. Hmm - is there no way around this or what could be a solution for me? – brother Jul 17 '12 at 11:34
On Express you cannot grow the database. For development you can buy a licensed Developer Edition which is unrestricted and costs about $50. – Remus Rusanu Jul 17 '12 at 11:39
3  
As your own comment has stated, you have reached the max size of the database. You have one of two options as far as I see it: 1. Upgrade your edition 2. Design your application so that it uses multiple databases therefore working around your size limit – Thomas Stringer Jul 17 '12 at 12:32
The issue is indeed the Express version being capped. However, your question states that you are worried about how or why the database is so large. That's something only you can answer. You could consider archiving data into a seperate database (i.e. data > 3 months), but that would probably require a lot of custom coding, and you already did state that you need to be able to store all the data. – user569711 Jul 17 '12 at 12:35
@brother -- out of curiosity unrelated to your question, does dbo.History contain two ntext fields? – echoScout Mar 4 at 20:57

migrated from stackoverflow.com Jul 17 '12 at 12:45

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.