当您达到 SQL Server Express 4GB/10GB 限制时会发生什么？
会发生什么样的错误？用户体验如何？您可以使用工具访问数据库吗？如果将其恢复到 4GB/10GB 限制以下怎么办？
What kind of error occurs? What do users experience? Can you access the database using tools and what if you get it back under the 4GB / 10GB limit?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
据我了解，您将开始看到事件日志中出现异常消息，例如：
如果您可以减小数据库的大小，则可以像以前一样继续添加等。无论数据库大小如何，工具都应该继续工作。
希望这有帮助！
As I understand it you will start to see exception messages appear within your event log, such as:
If you can then reduce the size of the database, you can then continue to add etc as before. Tools should carry on working regardless of the database size.
Hope this helps!
为时已晚，但我测试了它。 SQL Express 2008 R2 每个数据库的最大大小为 10240 MB。到达此位置后，我在插入时遇到此错误：
之后我重新启动 SQL 服务，它停止并启动没有问题。我仍然可以运行“选择”、“更新删除”命令。 （我确实测试了更新命令并且成功了，但我认为如果你更新到更大的东西可能会抛出错误！）
It is too late but I tested it. The maximum size for SQL express 2008 R2 is 10240 MB for each database. After I reached that I got this error on insert:
After this I restart the SQL service, It stopped and started with no problem. I still could run Select, update delete command. (I did test update command and it was success, but I think If you update to something bigger it may throw error!)
您可能会看到如下错误：
或者这个：
这是来自我们的错误日志。
You might see an error like this:
Or this:
That's from our error log.
用户遇到应用程序无法运行的情况，通常是从出现过多的奇怪错误开始的。
任何基于 Express 构建的应用程序都应该将其作为其初始规划的一部分 - 我们如何缩小尺寸。计划——只要可以，我们就会担心它，直到有人不得不支付许可费。这通常是在经历了大量的挫折、停机、调试之后，有人认为问题出在驱动器已满，其他人认为问题是新代码发布等，挫折等等，并且用户花了一些时间寻找另一个供应商谁能提前计划。我确信这正是你正在做的事情。 感谢您首先考虑您的用户！！！！！！！！！
Users experience the application not working, usually beginning with strange errors that have bubbled up way too high.
Any app built on a Express should have as part of its initial planning - how do we keep the size down. The plan - we'll worry about it whenever is ok, until someone has to fork over the license fee. And that is usually after tons of frustration, down time, debugging, someone thought the problem was a full drive, someone else thought it was that new code release, etc, frustration, etc. and the user has spent some time looking for another vendor who can plan ahead. Which I'm sure is exactly what you are doing. Kudos to you for thinking of your user first!!!!!!!!!
增加大小的操作将失败，例如插入、更新。您仍然可以访问数据库并对其进行维护以缩小大小。
我会设置一些维护作业，在数据库达到此大小之前提醒您，这样您就可以防止任何数据丢失。
Actions that increase the size will fail, e.g Insert, Update. You will still be able to access the database and run maintenance on it to bring the size back down.
I would setup some maintenance jobs to alert you before the database reaches this size so you can prevent any data being lost.
也许您将无法插入更多数据，但您可以选择。
Probably you won't be able to insert any more data, but you will be able to select.
如果我没记错的话，当它发生在我们身上时，数据库就停止了。我们必须进行备份，以清理出足够的空间来进入并解决问题。
您可能想知道 SQL Server 2008 Express R2 现在有 10GB 的限制，因此可能值得升级。
If I remember correctly, when it happened to us, the database just stopped. We had to do a backup to clear enough space to get in and resolve things.
You might like to know that SQL Server 2008 Express R2 now has a 10GB limit, so it might be worth upgrading.