MCPalmetto
IS-IT--Management
My company is wanting got upgrade to Micros 3700 v.5.2 from 4.7. We are being told it can happen but we will lose our Sale Total Data? Has anyone else ran into this when upgrading?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Micros 3700 Upgrade Loss of Sale Total Data 1
- Thread starter MCPalmetto
- Start date
- Status
DJensen999
MIS
- Jan 27, 2014
- 145
Most Micros installers will automatically clear system totals before running the database conversion step to prevent unforeseen issues. This is not required in most cases - but if your database is in iffy shape, it may come down to it.
- Thread starter
- #3
MCPalmetto
IS-IT--Management
I have been told by our vendor that in order for a successfull upgrade all data must be deleted. This doesn't make any sense to me because you shouldn't have to delete any data, it should come over clean. Thanks for responding...
-
1
- #4
They are full of crap! You can do it the issue is that in the conversion of the data depending on the size of you db it can take an hours or hours as in many and no way to tell.
My old office always skirted around the issue as how to bill the customer? for how many hours? BUT when pushed they did it.
We would take a copy of the db and convert in our office as it could run all day if it had to. Then used the converted db for the upgrade.
Depending on the service schedule customer would lose a day or two of date when db's swapped. Print those days out and file away for if and when needed.
My old office always skirted around the issue as how to bill the customer? for how many hours? BUT when pushed they did it.
We would take a copy of the db and convert in our office as it could run all day if it had to. Then used the converted db for the upgrade.
Depending on the service schedule customer would lose a day or two of date when db's swapped. Print those days out and file away for if and when needed.
That's probably so Micros can upgrade the db ahead of time in their office. I've done a few in-place upgrades and they're a pain. You can't upgrade directly from 4.7 to 5.2. You have to go 4.7 => 4.11 => 5.0 => 5.2 prerequisit => 5.2MR1a . The upgrade process consists of backup up the DB, rebuilding it, running the conversion, and backing it up again. Doing this with a database full of totals can take take a long time depending on it's size and the speed of the server. One of my databases is about 1.2G and each version upgrade took about 4 hours. I've also run into a few databases that tanked so badly going form 4.11 to 5.0 that the encryption got corrupted and the server had to be re-imaged. Part of the process also includes rerunning CAL on all the workstations, which can't be done until the server upgrade is completed. Depending on how many you have, this could add another hour or so to the total upgrade time.
When I started my upgrade rollout I put all of our restaurants onto Res4.11 as a first step. They're all running that way while I'm working on the 5.2 upgrades. Before upgrading to Res5 I test the 4.11 => 5.0 conversion for the database on a test server in my office to see if there are any problems. Micros could probably do this for you as well, but it takes longer so the upgrade will cost more.
There's another option if you're replacing your server and not upgrading the OS on your existing. Change the IP/Name on the Res4 server, disable CAL, keep it on your network and access it through remote desktop. That way Micros will be able to blow out your totals and give you a nice clean upgrade, and you'll still have your historical totals.
When I started my upgrade rollout I put all of our restaurants onto Res4.11 as a first step. They're all running that way while I'm working on the 5.2 upgrades. Before upgrading to Res5 I test the 4.11 => 5.0 conversion for the database on a test server in my office to see if there are any problems. Micros could probably do this for you as well, but it takes longer so the upgrade will cost more.
There's another option if you're replacing your server and not upgrading the OS on your existing. Change the IP/Name on the Res4 server, disable CAL, keep it on your network and access it through remote desktop. That way Micros will be able to blow out your totals and give you a nice clean upgrade, and you'll still have your historical totals.
Quick question:
Doesn't micros erase historical data older than 13 months ?
Doesn't micros erase check details older than 15 days ?
Are you aware of any solution to have your checks in your own database where you can run reports without autosequence ?
Doesn't micros erase historical data older than 13 months ?
Doesn't micros erase check details older than 15 days ?
Are you aware of any solution to have your checks in your own database where you can run reports without autosequence ?
Historical data retention is programmable. You can keep posted data for years if you want, but the database will get pretty big.
Check detail is purged after 14 days, but can be held longer if you have transaction analyzer.
Reports can be written on any data in the database, including check details, if you have a copy of Crystal Reports. They're all run through Autosequences & Reports or Report Explorer, but don't need to be linked to an autosequence unless you want them automated. The only other option is a 3rd party reporting tool like Avero, MyMicros, Mirus, or the one you're writing.
Check detail is purged after 14 days, but can be held longer if you have transaction analyzer.
Reports can be written on any data in the database, including check details, if you have a copy of Crystal Reports. They're all run through Autosequences & Reports or Report Explorer, but don't need to be linked to an autosequence unless you want them automated. The only other option is a 3rd party reporting tool like Avero, MyMicros, Mirus, or the one you're writing.
In the POS configurator, go to the Reporting tab, Historical Totals button.
The first tab in that screen, Descriptor, has all of the totals that can be configured and the historical total class links.
The second tab, Classes, is where you set the tracking group and retention time for each class.
The first tab in that screen, Descriptor, has all of the totals that can be configured and the historical total class links.
The second tab, Classes, is where you set the tracking group and retention time for each class.
As someone who works for a dealer, I can tell you that while we can do the upgrade without clearing totals, we only ever do it for the simplest of setups. If they have ANYTHING custom, or anything that might break between conversions, we won't do it. We stage it in our labs first. So why clear totals? Because whats the point of having sales that are probably missing weeks worth of data? That just creates massive headaches for us down the road. Plus, during the conversion, it makes for a great time to clean things up. It is exceedingly difficult to delete anything in Micros with totals associated with it; why not take the opportunity to delete old employees and menus?
Clearing your totals will make for a far smoother process. Your old computer is yours - put it in a closet or give it to your accountant for historical data.
I've done a few upgrades where I did it on the spot, but generally speaking it takes me about 2 hours to upgrade from 4.6 to 5.2 - and thats without rotating keys or doing a rebuild, and a database no more than 700mb. Sometimes we can't even get a database to upgrade. We had a site recently where it took three weeks of troubleshooting to get the damn thing to upgrade because the various pre-convert scripts kept failing on something that we simply couldn't easily identify. Shit happens..
Clearing your totals will make for a far smoother process. Your old computer is yours - put it in a closet or give it to your accountant for historical data.
I've done a few upgrades where I did it on the spot, but generally speaking it takes me about 2 hours to upgrade from 4.6 to 5.2 - and thats without rotating keys or doing a rebuild, and a database no more than 700mb. Sometimes we can't even get a database to upgrade. We had a site recently where it took three weeks of troubleshooting to get the damn thing to upgrade because the various pre-convert scripts kept failing on something that we simply couldn't easily identify. Shit happens..
- Status
Similar threads
- Locked
- Question