The Forum has been Updated
The code has been upgraded to the latest .NET core version. Please check instructions in the Community Announcements about migrating your account.
My recent migration from Access to MS SQL went well and performance has been great. But I started getting the error "Could not allocate space for object 'dbo.FORUM_REPLY' in database..." Because my host limits SQL Server databases to 200MB, I need to remove older topics.
But my archive function isn't working. It either says no topics could be found, or shows a string of dots. I can delete previously archived topics, but can't archive anything new.
I went back to my previous installation to test archive with the Access database and it works fine. So, I assume the migration has caused this issue.
Any ideas?
But my archive function isn't working. It either says no topics could be found, or shows a string of dots. I can delete previously archived topics, but can't archive anything new.
I went back to my previous installation to test archive with the Access database and it works fine. So, I assume the migration has caused this issue.
Any ideas?
نوشته شده در
You can't mass delete topics, unless you archive them.
I think the level of effort you are needing to go through is a waste of time and patience. There are too many decent hosts without those ridiculous space limitations for SQL Server databases.
I think the level of effort you are needing to go through is a waste of time and patience. There are too many decent hosts without those ridiculous space limitations for SQL Server databases.
نوشته شده در
I made room in the database and tried archiving again. But now it only archived the REPLIES in the selected forum. All the old topics are still in the forum, with zero replies visible.
What a mess...
What a mess...
نوشته شده در
I agree it's too small. Especially since I believe they limit MySQL at 1000MB. Don't know the reason for the difference?
And I know that archiving won't reduce space, but I need to archive old topics before I can delete them ... right?
And I know that archiving won't reduce space, but I need to archive old topics before I can delete them ... right?
نوشته شده در
To be honest, 200MB as storage space is simply ridiculous. At this day and age, having to delete posts because you have such low database storage limits... well I have said it.
نوشته شده در
Off the cuff I'd say it's related to the limit in database size. Snitz makes a copy in the Archive tables before it removes the original - so if there's any interruption there's always at least one complete copy. If you're up against the size limit, you probably don't have space to create the initial copy.
As an aside, this means that archiving isn't going to really change the amount of SQL Server space available since all you are doing is shuffling content from the main tables to the archive tables. There are benefits to this, just not reducing your overall database size.
I'd see if your host can allocate more space. I'm actually surprised at that particular size limit as that is awfully small, and most hosts these days have adjusted their size constraints to accommodate the relative glut of relatively cheap storage available now. I'd get into more on hosting, but that sort of thing is off-topic here.
As an aside, this means that archiving isn't going to really change the amount of SQL Server space available since all you are doing is shuffling content from the main tables to the archive tables. There are benefits to this, just not reducing your overall database size.
I'd see if your host can allocate more space. I'm actually surprised at that particular size limit as that is awfully small, and most hosts these days have adjusted their size constraints to accommodate the relative glut of relatively cheap storage available now. I'd get into more on hosting, but that sort of thing is off-topic here.