Sims SQL 2016 to 2019 In place upgrade

[BOOT]

Only issue I had was that the upgrade leaves the database files in the original location.

I'll probably move them at a later date as it's a bit complex.

It's all been working fine since. Maybe even a little more reliable. 🤞

[webbobfc]

Are the ODBC drivers not required or are they reinstalled in the upgrade?

 

Cancel that don't think it needed.

Edited July 8 by webbobfc

[webbobfc]

Uninstalled what @BOOT suggested, rebooted the server and the upgrade ran through fine. All seems to be working, checked a few records, ran a couple of reports.

 

Give it a few days make sure all OK and run the summer update. Cannot wait for ISAMS...

[SlightlyWonky]

Just a few notes post upgrade.

 

Update the Binn location on SOLUS3:
Browse to Environment – Targets – Server. For each server/product listed highlight it and click Edit: 
Update the Binn folder to the location for the new SQL Server installation. 
<add you new Binn location>
Click Save.

Install latest SQL 2019 Cumulative update:
Download SQL Server® 2019 for Microsoft® Windows Latest Cumulative Update from Official Microsoft Download Center

[ITGuyNW]

So our migration initially went well, with SIMS and the SQL migrated to a VM.

 

However.

 

A week later, our Veeam backup failed with a "used by another process" error and now I cannot merge/restore back to the original parent. 

 

I've asked if we can get SIMS put back on the host instead of a VM. They make me incredibly uneasy.

[Boredguy]

That sounds more like a veeam/SQL issue more so than it just being because you've moved to a VM.

 

It depends what file it thinks is in use, but in days of old I'd often stop the SQL service before doing some of my backups to ensure we didn't get errors.  Not such an issue now as our backup solution actually integrates with SQL to perform the backups, plus we also backup the whole VM from the Host backup for additional belt and braces (does mean we can restore the whole VHDX file instead of the fun of just the SIMS SQL and remembering to run the right commands to remerge the user accounts)

Edited August 5 by Boredguy