You’re offline. This is a read only version of the page.
Good Day everyone,
I'm gonna try to explain my situation as much as I can. i'm running RMS 2.0 with HQ and 17 stores. Last year when most of the 17 stores were added, I overgrew the 4gb limit that came with SQL 2005 express, so I upgraded to the SQL 2008 express that comes with 10gb. that didn't last that long. So every few month i'll run a query and delete journals from the HQ database until just few days ago where I had to delete all the journals prior to August 2017 and that gave me a result of 89% usage. At this point I knew I had to come up with a different plan ASAP like purchasing a standard SQL license. in order to buy myself few extra days, I used a query to shrink my database and that's when my problems started. instead of shrinking it, it put the database back at 100% usage. I also deleted the database from the system since I have a back up and I thought it will be easy to restore it. the problem now I have is that I keep getting errors when I try to restore the data from a backup. I get the same error message on both computers
.
If anyone have any ideas, please Help. Thank you.
*This post is locked for comments
I have the same question (0)
Awwtttssss,
This is much more in trouble :(
We have also this type of scenario which we encounter on our HQ Database. We have 90plus store, no journal upload on HQ so we wont have much database increase daily, we run truncate table log daily so we can still maintain the speed of thransactions and connections.
As of now we have 100GB store on our Server which we run by SQL 2008 R2. What weve noticed was data from branch cant be uploaded here such as sales. So we truncated our database to80GB so we can recieve data and have no idea what also to do for this data gathering transactions from branch.
On your case, I think the backup database you have is not 100% error free. Meaning your truncate script affected your backup file. Do you have a backup with the original database? What we do on most cases we backup and restore it on new name of database. Then the existing one will be edited and we run some truncate script and we've loss some data but it still working.
Share
Report
All responses (
Answers (
