Click here for FULL Migration Document Package
Please refer to the FAQs at the bottom of this outline if uncertain whether to use SQL Express or SQL Standard, or if there are other questions about specifications and documentation.
This document is intended for an RFMS installation to SQL Server Express on Windows Server Standard Operating System. It can be adapted to other versions of SQL and Server Operating Systems, as long as they meet our System Recommendations.
To reduce the amount of time required to migrate, we recommend the technician do step 1 while the old server is still running before progressing to step 2 after-hours. Please keep in mind any work done on the old server after the backup completes will be lost. When the technician has made the backup, all employees should not enter new data until the new server is up and running.
Clients: please have the certified technician research and plan this process in advance.
Tech-Assisted Migration Service:
We offer a fee based after hours service where one of our techs will work with your local technician to perform the migration, after support hours. To purchase a paid migration service, please contact your Cyncly/RFMS Account Manager to request a migration quote. Alternatively, submit a request to the help desk at rfms-help@cyncly.com, and your request will be forwarded to your Account Manager.
Note: Our Technical Support Desk hours are 8:00AM - 5:00PM CST, and our technical team will be available for any questions during that time. Please note that support is done on a first come first serve basis and we are not able to schedule dedicated support for migrations during these hours. If direct assistance is required to complete a migration, a migration service must be purchased.
If the client is running RFMS version 9.6 or earlier, the client will need to purchase a conversion service from RFMS before migration. The client’s Account Manager will need to be contacted for information regarding conversion. Contact the AM by calling RFMS at 800.701.7367 or by emailing sales@rfms.com.
Disclaimer:
These documents are not designed to be a replacement for local, certified IT Professionals. RFMS recommends using a qualified technician for all tasks described in this document. IT best practices are beyond the scope of this document and failure to engage local IT professionals familiar with those standards can result in catastrophic consequences. It is important to understand that many of these processes need ongoing maintenance.
IMPORTANT!Before performing the migration check for the following services on the existing server(s). If any exist, contact the client's RFMS Account Manager to schedule service reinstallation after the migration. Follow this link for contact details of AMs by territory: Account Manager Territory Map
|
This article outlines four steps to properly migrate the RFMS installation to the new server:
- Install and Configure SQL
- Backup and Migrate RFMS and Database
- Connect Workstations
- Setup Automated Backups
Additional sections in the article:
Install and Configure SQL (click to go to article)
This step covers how to install and configure the SQL Server for use with RFMS. Before moving on to step 2, make sure that the technician has:
- Written down the new server name and instance name
- Written down which database on the old server has the actual RFMS data in it
- Found where the intended RFMS folder is stored on the old
Backup and Migrate RFMS and Database (click to go to article)
This step covers how to backup and move the data from the old server to the new server. Before continuing to step 3, please make sure RFMS works at the new server.
Connect Workstations (click to go to article)
This step covers how to setup the client workstations for use with the new server.
- If the technician is unable to connect the workstations, please see the troubleshooting section in the second part of step
- If the technician still cannot connect the workstations, contact RFMS for a more detailed troubleshooting document
- Put a ticket to RFMS requesting
Setup Automated Backups (click to go to article)
This step is often mistaken for being optional - it is not.
Carbonite and other online backup systems are what we refer to as file backup systems. They do not do the two crucial things covered in this step - create verified SQL backups, and keep the LDF file from holding on to any RFMS and SQL activity (which can grow until it fills up the hard drive and slow the client’s system down to a crawl).
Carbonite and others are useful for keeping copies of the RFMS folder and additional copies of backups. Bear in mind though that if the client tries to have constant cloud backups or file backups running on an active RFMS folder they will see a drop in performance. Try to have it only backup at a certain time in the day when there are no employees using it to avoid impacting performance. For more information, please see our Best Practices document.
Review Best Practices (click to go to article)
Make sure the technician is intimately familiar with all of the Best Practices contained in this document as these are extremely useful for making sure that the client’s data is as safe as it can possibly be.
Setup a Practice Database (click to go to article)
This document is not only useful for creating an environment for training employees but gives an exceptionally safe way to test updates and the integrity of backups in accordance with our Best Practices document.
FAQ's regarding SQL Express vs. SQL Standard
- Can I use as large of a database as I want with SQL Express?
- You are limited to 10 GB for a database if you are using Express.
- My database is 9 GB and I have 35 users, but it is still so slow. I thought SQL Express supports databases this large?
- SQL Express DOES support up to 10 GB for a database, but there is an important memory limitation – after approximately 1 GB of database memory use, the rest is pushed to the page file of the hard drive and can be considerably slower, particularly under higher loads. We recommend using SQL Standard after a database is 1 GB, or you have approximately 15 or more users. This second metric is due to a higher growth rate of a database as you have more users entering data.
- SQL Standard is expensive. Does my business really need this?
- Possibly – refer to the above questions. If in doubt, SQL Standard does have a six month trial, which should be more than enough time for a business to test with and make a sound financial decision on whether the purchase is worth the cost.
- I tried it and it helped. But I read online that an SSD can read and write data many many times more rapidly than a mechanical drive. My database is only 5 gigabytes. So why do I need SQL Standard if it’s just going to put it in memory?
- This is a common question, with two common misconceptions. DDSs can and do result in tremendous reductions in load times for modules from the app server and query times for larger express databases. But they are not a panacea – a faster hard drive can never replace proper configuration and other weak links in an environment. They are also not ticking time bombs waiting to delete your data, but SSDs are not all created equal – ONLY use an enterprise grade SSD from a reputable brand on a server.
- I’m still not sure / I have other questions about your SQL, server, or network specifications. Do you have documentation on this?
- Yes, and we absolutely recommend checking into it before beginning an install OR migration. It can be found here: https://rfmsinc.zendesk.com/hc/en-us/articles/201981506-RFMS-SQL-System-Specifications.
Comments
Article is closed for comments.