SQL Server appears because the filegroup ' PRIMARY ' full solution is likely to be caused by insufficient disk space left

A generic virtual host provider provides customized database space by restricting the size of the database file. This restriction still exists when you restore files from a virtual database space back to your own server.
Locate the database file

Just a few more data files.

Workaround:
1. Check that your disk has enough space left, and clean up the disk if there is no disk space left.
2. Check your disk partition format: If it is FAT16, then the data file can only be 2G, if it is FAT32, the data file can only be 4G, the NTFS partition does not have this limitation.
3. Check to see if you have limited database file size:
Enterprise Manager--right--Your database--Properties--File growth limit--if there is a limit size, remove the limit.
4. Check your SQL version, and if you use MSDE, limit the data file to 2G max.
5. You can also add a new data file for the primary group to solve this problem
ALTER DATABASE name add file (name = logical file name, filename = ' C: actual file name. ndf '. (It is actually more convenient to select the database "Properties" database file through Enterprise Manager.)

By adding a ndf, the problem is solved!

SQL Server appears because the filegroup ' PRIMARY ' full solution is likely to be caused by insufficient disk space left