Thank you for sharing your experiences with R6 and SQL Server 2019, Charlie.
At this time, R6 has not been thoroughly tested with SQL2019 - it is something that the Recorder 6 Steering Group has given consideration to, with Mike Weideli, but our main focus to date has been on progressing the feasibility study for the 'successor / parallel system'. I will double-check where we're at with this and update users via the R6 e-news.

The attached shows another example - data from the taxon occurrence comment column is being put into the species matching screen. Looking at the #Species table, this looks genuine - ie the field "Species_Name" has values of "SM4 recording in mid spring" and "SM4 recording in mid summer". However in the #Master table, these values are in the field "SYSTEM0100000006" which I believe is correct (it's the Taxon Occurrence Comment field not the Species field?).

Going backwards in the import wizard, setting the comment column to ignore and then proceeding works as expected. Going backwards a second time and setting the comment column back to taxon occurrence comment and proceeding also works fine.

I'm stabbing at the dark, looking behind the scenes with the import wizard so if anyone who knows better wants me to look at anything specific, let me know!

Another different one - grid ref appear in Location matching screen. Again, going backwards setting both the location and grid reference column to ignore, going forward in the wizard, then going back and setting the columns again and it then works as expected.

A thought - it may not be a problem with SQL server, it may be a problem with Recorder itself? Something going awry with the import wizard after multiple imports. We're on 6.30.0.291 and have been for a while, but I haven't noticed this problem before we upgraded the SQL server.

I'm also regularly (once a day?) getting the error "Cannot continue the execution because the session is in the kill state." with the import wizard.

Another new error for me with the import wizard (the screen prior to hitting "import"):

Closing and trying again with the same file works fine.

The import wizard has just created me an import file with empty TAXON_DETERMINATION TAXON_LIST_ITEM_KEYs; this obviously then failed to import.

We still haven't been upgraded to the latest CU version (stuck on GDR, I'm hoping we can get updated soon..). What version are you on Mike? We're running:

Microsoft SQL Server 2019 (RTM-GDR) (KB4583458) - 15.0.2080.9 (X64)
    Nov  6 2020 16:50:01
    Copyright (C) 2019 Microsoft Corporation
    Standard Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor)

Certainly not an R6 issue - never had any of these problems before we upgraded!

We've finally had our production server upgraded to the latest cumulative update (CU15) and so far, touch wood, we haven't had any errors yet. The issues with the report wizard seem to be solved, but I haven't done any large imports; that's next to test on my list.

Our version string is now:

Microsoft SQL Server 2019 (RTM-CU15) (KB5008996) - 15.0.4198.2 (X64)
    Jan 12 2022 22:30:08
    Copyright (C) 2019 Microsoft Corporation
    Standard Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor)

We moved to SQL Server Express 2019 (15.0.2080.9) this year and I've not imported data into it yet. Most of our data is going into Postgres.
I have only noticed one oddity but don't know if it is version related. I have a site with an LWS designation that on reporting from SSMS does not show up. I've tried several things to see why but to no avail.

We've been on 2019 since December 2021 and the only ongoing issue is the out-of-order sorting in the import wizard. This just seems to be a display issue and doesn't seem to affect imported data in anyway - indeed, clicking on the column header and it sorts it fine, "like how it used to be":

The important thing is to make sure it's updated - it took a while me to convince out IT support that there were 2 years of updates to apply...