Problems with MS SQL 2008 Express database

Question

Microsoft

There was a problem of exhaustion of the size for a DB. mdb began to weigh the maximum 10000+ MB. What are the methods to continue working with it? It cannot expand further, compression does not occur. Can you somehow add an additional mdb with disabling the current one? I don't know how to do it. But there is a need to work with the current mdb file in the future.

Answer 1

It seems that the answer is obvious, upgrade to Workgroup , the price of course bites, but what did you expect when starting to work with MS SQL?
There is another option, you can write a converter in MySql or Postgresql, it will most likely not be difficult to write the converter itself, but it all depends on the applications that use your database. How difficult it will be to migrate these applications to the new database.

Answer 2

Have you tried moving the tables to another *.mdb and linking to the current one?

Answer 3

Tried - doesn't even let me create an additional mdb because the PRIMARY filegroup is full

Answer 4

Then, apart from switching to another database, I can offer nothing.
And with normalization and archiving there is no chance at all?

Answer 5

I would look at how much the indexes weigh, and how much the data, which indexes were called, how much, maybe the "garbage" is full.

Answer 6

if the application can work with two databases at once, then connect a new one, we do this with Sharepoint, there is a separate database for each directory

Answer 7

Revise indexes, statistics.
Data aggregation is possible (if the business logic allows).