We are about to start the migration to SQL Express on non secondary schools.
Any pitfalls to be aware of?

We are about to start the migration to SQL Express on non secondary schools.
Any pitfalls to be aware of?

what are you migrating from?
I have tested yesterday on test system, from SQL 2005 to SQL 2008 64bit work fine. Except one problem, we have active directory integrated (Auto logon) one of user name was changed and that was not updated in SIMS, corrected that and its work fine.

@Nephilim
SIMS 2005 - 2008 SQL
@RCS_USER
I have done 2 test systems and no problems, but a live school and old servers?![]()

New SQL instance has to be a named instance and watch out for the installation drive install path as some schools install to a different drive that's all, did it yesterday from 2005 - 2008 ent and no apparent problems.

We are about to start ours too. We are hopefully automating the process as much as possible using CentraStage. It worked a treat on the test system. But on a live site, you never can tell.
The annoying thing will be the pre-requisites of getting .Net 3.5 SP1 and Windows Installer 4.5 on the servers. 4.5 reboots after install and if you need to install .Net 3.5, you have to reboot again before installing SQL. Luckly, we can schedule it as an overnight process.![]()

Luckily we put 3.5 on ages ago. Running SIMSSQLInfrastructure.exe before had and it seems happy with the setup.
?The annoying thing will be the pre-requisites of getting .Net 3.5 SP1 and Windows Installer 4.5 on the servers. 4.5 reboots after install and if you need to install .Net 3.5, you have to reboot again before installing SQL.
Different automation but I did SQL pre-reqs as "Phase 1" a while back and didn't need a reboot for powershell1 (required for Management Studio) or dotNet 3.5SP1, just MSI4.5.
[Phase 2 is SQL 2008 Express w. Tools and SP1. Phase 3 is running the Capita migration util etc.]
There are currently 1 users browsing this thread. (0 members and 1 guests)