How can I establish whether it would be a good idea to upgrade from Express to Standard?

All we need is an easy explanation of the problem, so here it is.

In Express 2019 running on Linux, If I right click my database I can see that it is size 11506 Mb with 1963 Mb free space. Currently showing 17 users.

I am trying to work out whether it would be better to delete records or upgrade.

Given the cost to upgrade is significant, how can I establish what performance benefits we might gain?

If we trial upgradeing can we roll back?

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

I am trying to work out whether it would be better to delete records or upgrade.

This is a business decision, not a technical one. Do not just delete data “to make space” – if the data is important and must be retained, then the organization will have to find a way to pay to keep it around.

You can’t downgrade SQL Server in the way you’re suggesting.

If you want to explore the possibility of upgrading to a paid edition of SQL Server, I suggest setting up a new server with Developer Edition installed (Developer Edition is free). Then take a backup of your current database, restore it to this test server, and run a sample of your workload against that.

If you decide you need to upgrade to Standard Edition, this method (backup & restore) is also how you’ll move your data over. I do not recommend performing an in-place upgrade (which is what your proposed method suggests).

If you’re currently satisfied with the overall performance of your setup, and only looking into upgrading due to the database size limitations of Express Edition, you have a few options:

  1. Create a second database which mirrors the first, splitting the data between the two. This will require application changes
  2. Move “old” data to a second (archival) database based on age, deleting it from the original database
  3. Just delete the old data altogether
  4. Implement page- or row-level compression on your tables & indexes to buy some more time. But eventually, you’ll hit the 10GB limit anyway.
  5. Migrate to a cloud-hosted database platform like Azure SQL DB where you’ll pay for what you use

Options 2 & 3 should only be considered if the business requirements for the data allow for it. Option 5 should only be considered if the business’s data governance policies allow for it.

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply