ERROR: “Could not allocate space for object ‘X’ in database ‘Your Database’ because the ‘PRIMARY’ filegroup is full”

“Could not allocate space for object ‘X’ in database ‘Your Database’ because the ‘PRIMARY’ filegroup is full” error Issue

You receive an error similar to: ‘Could not allocate space for object ‘X’ in dabase ‘Your Database’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting auto growth on for existing files in the filegroup.’ when browsing to your site.

Cause
Your database is either too big or had an artificial size limitation imposed on it by a previous host.

Resolution
The following steps require Microsoft SQL Server Management Studio. If you do not have this installed on your local computer please follow the instructions at How To Connect to Your MS SQL 2008 Database and Disable Collation

  1. Open Microsoft SQL Server Management Studio.
  2. Right click [your database] and select Properties.
  3. In the left navigation window of the dialog box that pops up, select Files.
  4. In the Autogrowth column select the button noted in the image below and change them it to Unrestricted Growth under Maximum File Size.
    Change Autogrowth MS SQL Settings
  5. Repeat step 4 for the second file type.
  6. Click OK
  7. Reset your site (reset the web.config file b
    y renaming the files and saving it, then renaming it back.)

If you still continue to get this error, your database is over 4 GB in size.  You can shrink your database using the instructions at How To Truncate Your DNN Logs In Your MSSQL Database then follow the above resolution again.

via: https://support.managed.com/kb/a132/error-could-not-allocate-space-object-x-database-your-database-because-primary-filegroup-is-full.aspx

MariaDB adds NoSQL features to relational database roots

SUMMARY:MariaDB 10 is out, featuring a “Connect engine” that makes it easier to handle data from both traditional SQL databases and more web-scale NoSQL systems. The new functionality merits new editions of the MariaDB Enterprise and Enterprise Cluster products.

SkySQL has released new versions of MariaDB Enterprise and MariaDB Enterprise Cluster, promising that these editions will combine the consistency of traditional SQL database technology with the scalability of NoSQL.

It’s now almost a year since SkySQL merged with Monty Program, bringing back together a lot of the old MySQL team — around 50 of them, including Monty Widenius and David Axmark — to take on the current MySQL proprietor, Oracle, with the MariaDB fork of the venerable database system.

MariaDB was always pitched as a “bridge” between MySQL and NoSQL databases like Cassandra and LevelDB. Now the MariaDB Foundation has released version 10of the open-source database, bringing in several NoSQL-esque capabilities that make MariaDB Enterprise 2 a more enticing package.

The big addition is the Connect engine, which provides quick access to unstructured files, for example log files in a folder, from within MariaDB. Cassandra data can also be accessed from within MariaDB 10, and “dynamic columns” also allow NoSQL-style storage of variously-labelled objects in each row. Apart from that, MariaDB 10 is also supposedly much faster and more stable than previous versions.

SkySQL sales chief Dion Cornett suggested to me that enterprise users would find value in being able to glue together the various file and data formats they might encounter.

“What if your online store sells and fulfills orders from a broad range of different suppliers, and your systems must access and combine their inventory records — stored in different SQL databases from Oracle to MySQL to PostgreSQL to SQL Server?” Cornett posited. “Combining such different data sources together in real time has required a lot of hand-coded logic — a costly and time-consuming proposition.”

As for MariaDB Enterprise Cluster 2, a new user console and management API aims to simplify the deployment of Galera clusters, a movement that should appeal to those with high-availability needs.

via: http://gigaom.com/2014/03/31/mariadb-adds-nosql-features-to-relational-database-roots/