06-16-2017 08:46 AM
Although already compatible Act! V19.2 with SQL Server 2016 - I guess it is not possible to have a mixed SQL Server implementation...
Something like... Server With SQL Server 2016 and Remote user with SQL Server 2014 Express...
may be... at the time of restoring the remote database you get a message that refers to The database was created in a higher SQL version
In this case I suggest....
SUGGESTION if you have SQL Server 2016 on your server, before you install Act! On the remote user's computer ... create the instance manually with SQL Server 2016 Express (on the remote user's computer)
( Remember... Even on the server... you must manually create the instance SQL Server 2016 before installing Act! -- It's the best way for now - Later we will be able to have the Act! installer Creating by default the instance with SQL Server 2016 Express)
Yesterday I tried to upgrade the instance of a remote user (From 2014 to 2016) and I had problems
So... the best thing is that before installing Act! On the Remote User's Computer - Manually Create Instance with SQL Server 2016... If your server has SQL Server 2014 ... this is not necessary
DO NOT FORGET TO MAKE A DAILY DATABASE BACKUP...
Best regards and Happy Father's Day
06-16-2017 10:25 AM
Thank you for this suggestion.
For those of us who may not speak SQL, would you provide some guidance on manually creating the ACT7 instance, then finding/connecting when installing ACT v19.2?
I believe SQL Server 2016 Express is a free download - any other SQL tools or suite suggested?
06-19-2017 09:12 AM
07-10-2017 08:22 AM
No mapping between account names and security IDs was done
07-10-2017 09:22 AM
Thanks for replying, yes, it was possible to create the instance manually, but I just wanted to let you know what happens when someone tries to upgrade the instance.