HI BAustin,

The release notes are your best reference.

0. In the old software, make a backup (File | Backup), then

      from the Maintenance menu in the old software, under 'Database Utilities' choose the 'Check Data Integrity' item.  It should show 'DATA OK'

      Also from that menu, Under Database Utilities, run the Advanced Database Check.  It will ask if you want to make a backup.  You absolutely do.

1. Install server software on new server

       Install client (full) new software on at least one workstation.   You do not have to uninstall anything.

2.  Restore the data file to the desktop, on the workstation that has the 2014 release installed on it.    (this can be the same workstation that you currently have the Premium 2009 F release installed on.  

The data will automatically be converted - Probably without issue, but if there is a problem contact Sage support.  If the file is large this will take a bit of time, since the conversion may convert 2009-2010, then 2011 to 2012, etc. 

The two parts of step 1 can be done in any order.  Take advantage of each opportunity that the software offers, to make another backup.   It takes a few minutes of time, but can save weeks of data entry.

The Connection Manager is back-compatible, installation on a server will not stop the 2009 version from working.  You could, for example, install the Connection Manager on the 2012 server one week and attach the workstation running the 2009 software to it, then upgrade the workstation the next week.  Probably if the 2009 software doesn't connect to data on the new server, the 2014 program won't, either.

I hope that helps, please post back.

p.s. I have seen posts where Server 2012 systems are problematic, when using various 'cool' Microsoft technologies to redirect, virtualize, or otherwise confuse the workstation about data storage.   Keep the number of moving parts to a minimum.   Use plain, ordinary file share on a 'real' volume that does not have VSS, compression, or encryption, enable tcp/ip through the firewall, and it should 'just work'. 

Thanks RandyW,

I am just lost on part 0 (Back up data using Sage 50 utilities, then from the Maintenance menu, check the data integrity, and then run the Advanced Database Check) Do I need to install Sage 50 on the old server first? Or do I need to install on new server first? Sorry for the lack of knowledge, I was just brought onto this company and have never used the Simply Family. Cheers,

Hi,

I made some edits to the first post.

Step 0 is getting the data ready, before you install anything or convert any data.  

Step 1 is getting the systems ready and testing.   There is a lot of flexibility here, since there is:

- back-compatibility of the Connection Manager / server database.  

- really no problem with having multiple years of the software installed.

(other than Explorer will associate '.SAI' with the last installation of any year.   This means that double-clicking on the file in Explorer will always open the last installation, instead of the right one.   However, opening the right version (i.e. 2009) will allow you to pick the unconverted (i.e. 2009 data. )

Step 2 is converting the data.    This is a one-way change to the database structure.

(BACKUPS are important.   If you need to bail out and go back to the 2009 version, this is your last chance.)

So your back-out plan at:

Step 0 would be "found a problem with the data, ABORT".

Step 1 would be "found a problem with the environment, Abort".

Step 2 would be "Could not convert the data, Restore from Backup".

Ok, Thanks so much for the clarity.

Backups I am not worried about. Got it covered.

This is what I've learned about Sage 50 backups:

The Sage 50 backups (with 'verify' and 'compact data' selected) should be run regularly, since it will tidy up the database when run.

If you absolutely must back up the data directly, if you can, configure the script or backup software to check for the presence of a 'process.pid' file in the company data folder (folder with the same name as the 'company file' with a '.SAJ' extension.  If the process.PID file is there, someone is logged in, and the data folder should be skipped.  

And on the volume where the live Sage 50 data is stored:

- Never use VSS  (it's great, for applications that are VSS-aware, MySQL isn't)

- Never allow any kind of virus scanning.

- Disable compression.

- Disable encryption.

- Turn off any disk 'optimization' or 'defragmentation.  

- Mirror, or use RAID 5 on the disk

So a most of those things were learned by research, a few by doing it the other way and wishing I hadn't.  Like all open source, and free advice on the internet, if you follow my advice and something breaks, you get to keep both pieces.

Randy,

Thanks a ton!! Not a hitch and followed step by step.

Just a note, on earlier comments, We run Server 2012 R2.

It is a Client Machine on a VM ESXi 5.1.

Your steps proved to be perfect and not one issue.

Cheers,

Brent Austin

Randy,

Thanks a ton!! Not a hitch and followed step by step.

Just a note, on earlier comments, We run Server 2012 R2.

It is a Client Machine on a VM ESXi 5.1.

Your steps proved to be perfect and not one issue.

Cheers,

Brent Austin