jschultz
commented
3 years ago I didn't realise QSR provided any information at all about the SQL Server version. In any case well done for working out and configuring the correct one.
From what you describe it certainly looks like NVivo v12 has changed at least the name of one of its tables. However, since Annotation is the first table that NVivotools tries to access, it may be that something else has gone wrong.
Since you have managed to connect to the database, are you able to do a dump of its structure and we can take a look? Like pretty much everything created by Microsoft this is something that should be trivial but isn't. You may find it simpler to export to NVivo for Mac format which uses SQL Anywhere databases and do it from there. Although that still leaves the problem that there are small differences in the formats between Windows and Mac versions, it should be enough to tell us whether the table names have changed.
gdzqzzx
Hi Johnathan,
Any chance you can adjust NormaliseNVP for windows NVivo 12?
Version 12 uses Microsoft SQL Server Express LocalDB 2014 SP3 seen from here - I have downloaded this and used the steps as directed.
There is an error that 'nvivotools' user cant be logged in. The server output is as follows:
2021-02-11 14:27:51.09 spid52 The database 'nvivo10796' cannot be opened because it is version 869. This server supports version 782 and earlier. A downgrade path is not supported. 2021-02-11 14:28:12.43 Logon Error: 18456, Severity: 14, State: 38.
Does this mean the server is wrong?
Update:
Installing SS Express 2017 and changing the InstanceVersion to 'MSQL14' no longer throws a server user connection error - taking the process through to the Normalise table creation section but is now failing with sqlalchemy.exc.NoSuchTableError: Annotation. Is this because the tables in v12 have changed with new structures and names?
Many thanks for your work to date, If we can get this to work it would be a lifesaver!
Cheers, Mike