SQL Server Versions for Jiwa

[SBarnes]

Hi,

What versions of SQL server are supported under Jiwa 7.00.175 and Jiwa 7.01.00?

Is there a time frame / road map under which support for SQL 2008 and SQL 2012 will be phased out?

The reason for the question is we have a number of customers that need upgrading and we want to advise them if upgrading their version of SQL Server is a cost that should be considered as part of the process.

[Mike.Sheen]

Hi Stuart,

We currently support SQL Server 2008 R2 or later for any version of Jiwa 7. SQL Server 2008 may work fine, but we don't test against that - we test against 2008 R2 so that's the minimum version we officially support.

We don't intend to discontinue support for older versions, but may do if we produce a release of Jiwa which is reliant on features only available in newer versions of SQL Server. We cannot give any guarantees we won't do that - but I think it is quite unlikely we'll require a version newer than SQL 2008 R2 in the foreseeable future.

Having said that, it's a good practice to ensure your software (OS, SQL Server, and so on) are never more than 2 major versions or 5 years old.

Mike

[Scott.Pearce]

Here's a flag - Jiwa fails to create demo data on SQL Server 2017. I believe we ship some SQL 2016 assemblies that handle the bacpac import and they can't talk to SQL Server 2017. We'll likely fix this in an upcoming service release.

EDIT - the workaround is to import the Jiwa bacpacs (found at "INSTALLDIR\Data Files") using management studio.

[SBarnes]

Thanks Guys,

Thanks for the update, speaking of the bacpac files would is be possible to setup a database in Jiwa and then create a new bacpac to use multiple times?

And is so what would be the steps needed?

[Mike.Sheen]

would is be possible to setup a database in Jiwa and then create a new bacpac to use multiple times?

And is so what would be the steps needed?

Hi Stuart,

Any database you can export to a bacpac using either Jiwa or SQL Management Studio.

Using Jiwa, at the login screen simply press the databases... button and then select "Export a Jiwa database":

Export bacpac

Jiwa_Export_Bacpac.PNG (17.63 KiB) Viewed 8026 times

Using SQL Management Studio, right click the database, select Tasks > Export Data Tier Application:

SQL Management Studio Export Data Tier Application

SQL_Management_Studio_Export_Data_Tier_Application.PNG (55.89 KiB) Viewed 8026 times

That will produce the bacpac file.

You can then copy this bacpac file to the customer server, and either restore it via SQL Management Studio, or even Jiwa with some extra steps.

Using SQL Management Studio, right click databases and choose "Import Data Tier Application":

SQL Management Studio Import Data Tier Application

SQL_Management_Studio_Import_Data_Tier_Application.PNG (14.91 KiB) Viewed 8026 times

Using Jiwa, you would need to rename the bacpac file to JiwaNew.bacpac and place it in the Program Files (x86)\Jiwa Financials\Jiwa 7\Data Files folder, overwriting the existing (probably best to rename the existing one first in case you want to revert). Then, at the login screen when you select the Databases... button and then select "Create a new Jiwa Database" it will use the bacpac "Program Files (x86)\Jiwa Financials\Jiwa 7\Data Files\JiwaNew.bacpac" to create the database.

Mike

[DannyC]

Can I get a quick update for 7.2.1 SR4...Is SQL Server 2008 R2 still supported?
Any plans to mandate minimum SQL Server 2012 or higher?

cheers

Danny

[Mike.Sheen]

Can I get a quick update for 7.2.1 SR4...Is SQL Server 2008 R2 still supported?

2008 R2 is supported, except if you're using the REST API - that requires SQL 2012 or later.

Any plans to mandate minimum SQL Server 2012 or higher?

Yes, 7.3 definitely requires SQL 2012 or later.

[SBarnes]

I think the bigger issue is Microsoft don't which means if someone has a problem with it they will be stuck.

There are parts of Jiwa now that won't work with it such as the Rest API.