Hi Julius,

You can select the database properties



And on the Files page select the data file and choose unrestricted growth.



If it's already unrestricted maybe you've hit the Sql Server 2005 Expres limit of 4Gb per database. More info here at the end of the page.
You can check database size on the General page of the database properties:



Let us know if this helped.

Best Regards
David Nunes

You can also check this post for further help:

www.outsystems.com/forums/discussion/9539/sql-server-database-error-primary-filegroup-is-full/

Hi devid

its working for me when i done this change in my database,but my company has 100 branches and all database have same problem but if i do this changes on all database is that gonna harm my head office server
or it will be have any problem 

Hello Vishal

Usually the transaction log growth is something that can growth if uncheck, so I recommend properly setup maintenance plans to control the size of the transaction logs.

For instance: 

• Non-production environments should be configured to use Simple Recovery model, instead of Full Recovery model. More info on https://msdn.microsoft.com/en-us/library/ms189275(v=sql.105).aspx
• Production environment, should have regular transaction log backups to control the growth of the transaction log, and eventually, some regular shrinking of the transaction log file. More information about SQL Server best practices available at www.outsystems.com/goto/sql-server-best-practices

If the problem is the database data files, then you need to size your databases according to the estimated data growth rate. If you're hitting on the 4GB database limit of SQL Server Express 2005 or 2008, then you either reduce the database set, or have to get some SQL Server licenses ...

Hope this helps to define an approach for large number of database instances.

Cheers

Miguel Simões João

Thanks Miguel but one another problem i am facing when i go for sp_spaceused for my database its shows me negative figure in the unallocated space field