Migrate/Update Access/SQL Application to run in a VM Environment
I have been asked to migrate/update an Access/SQL Application so it can run in a VM Environment on a true SQL Server; I have a general understanding to get started, but this is my first VM project, so step one is to plan for the unexpected. I request that you treat me as a novice when making suggestions.
Rather than write a novel about the function of this Access/SQL Application and to minimize suppositions, I would rather respond to questions about it.
To start this off, here is the current configuration ...
Standalone Workstation
Windows 10 64 Bit
Access Pro Plus 2013 (Front End)
SQL 2016 Express (Back End)
What would be the best approach and what pitfalls should be anticipated?
Rather than write a novel about the function of this Access/SQL Application and to minimize suppositions, I would rather respond to questions about it.
To start this off, here is the current configuration ...
Standalone Workstation
Windows 10 64 Bit
Access Pro Plus 2013 (Front End)
SQL 2016 Express (Back End)
What would be the best approach and what pitfalls should be anticipated?
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
So you want to convert this working environment to a physical or virtual environment ?
First of all, understand why are you going for a SQL Server Express Edition. I know that is a free version of SQL Server but it has limitations, like database can't be bigger than 10GB, it only uses 1 CPU and 1GB RAM. Besides many features aren't available in this Edition.
Are you aware of these limitations and willing to proceed anyway with SQL Server Express Edition?
Are you aware of these limitations and willing to proceed anyway with SQL Server Express Edition?
Also check out Gustav's excellent article:
https://www.experts-exchange.com/articles/23959/Deploy-and-update-a-Microsoft-Access-application-in-a-Citrix-environment.html
https://www.experts-exchange.com/articles/23959/Deploy-and-update-a-Microsoft-Access-application-in-a-Citrix-environment.html
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for all of the information; I have spent a great deal of time reading and there is still more to come. In the meantime allow me to clarify some aspects.
Andrew Hancock and Vitor Montalvão: Currently this access application is running on two separate workstations using SQL Express; each is independent of the other. The powers that be, have asked to move it to an SQL server and set it up to run from a VM environment. in anticipation of adding more users to share the workload.
Scott McDaniel: Yep, we will be on our own; hence my question. To quote an author, "Hope for the best, plan for the worst."
Here is my understanding of the suggested configuration; essentially everything will run from the VM; the users physical workstation does nothing but run the "Remote Desktop Connection" application.
Andrew Hancock and Vitor Montalvão: Currently this access application is running on two separate workstations using SQL Express; each is independent of the other. The powers that be, have asked to move it to an SQL server and set it up to run from a VM environment. in anticipation of adding more users to share the workload.
Scott McDaniel: Yep, we will be on our own; hence my question. To quote an author, "Hope for the best, plan for the worst."
Here is my understanding of the suggested configuration; essentially everything will run from the VM; the users physical workstation does nothing but run the "Remote Desktop Connection" application.
Well very quickly you could Convert and Migrate these existing machines to a virtual environment.
or do you want to move SQL Express databases to an SQL server....
or do you want to move SQL Express databases to an SQL server....
ASKER
Andrew, We are not moving SQL Server Express; we will have an "true" SQL Server.
Do you require any additional help by Experts, to select a solution and close this question ?
ASKER
There is much to do when moving into a VM Environment; so the best answer is read, read, read ...