Support for MSSQL database on the roadmap?

[activiti-admin]

Hello everyone,

we are just starting to think about introducing some kind of BPM system into our web application. After looking at jBPM (and beeing confused about the future of the project), I found Activity which looks very promising. Keeping a focus on standards is very appealing.

Is there any reason for only specifying certain databases? We would need support for MS SQL Server. I guess your will be using some kind of O/R Mapper (Hibernate?, JPA?), or will there be some database specific functionality?

Another question about the modeler: Will there be support for other activities than the "blank" task, e.g. userTask, scriptTask in the modeler? I could not find something about that on the roadmap.

Thanks,

Tobias

[thilka]

Forget about the second question, just found out that it could be specified in the properties section on the right. Just expected them to be "first class" elements.

[mschaefer]

Support for MSSQL would be great. If Activiti will be the "superdelux process engine" as expected we gonna use it in a project backed by an MSSQL database.

[michael_kimber]

Yep we would need SQL Server 2005/2008.

If its not a big job or just testing then and we decided to us Activiti then we could do this.

[bill1]

Hi, How about Oracle support? What's the general roadmap for database support? Thanks,

[mschaefer]

Hi, How about Oracle support? What's the general roadmap for database support? Thanks,

I think Oracle support is planned for 5.0.alpha3. See the roadmap: http://activiti.org/roadmap.html

Martin

[akakunin]

Hi!
As I found, Activiti used iBatis for working with SQL database. From ibatis documentation complexity of migration from one DB to another depends from complexity of sql-scripts used for working with DB (ibatis used directly SQL) - if standard SQLs used - migration should be easy. If some vendor-specific sql used - it may be a problem.

Since currently H2 is used as DB - I pretty sure migration to some other DB should be easy (if it work on H2 - it should work - with some minor changes on other DBs)

You can check this forum post for more details about other DB support (http://forums.activiti.org/en/viewtopic.php?f=4&t=17

[sebastian_s]

See also the post on the developer forum related to the support for Sybase. AFAIK Sybase and MSSQL are quite similar in some respects. Maybe you can coordinate your efforts there.

[sebastian_s]

I am trying to look deeper into what needs to be done to support sql-server. With the help of http://msdn.microsoft.com/en-us/library/ms378715.aspx I created the necessary sql-scripts for mssql and I also took the script which inserts example date and changed it to fit mssql. However I am now encountering a problem when I am calling the db.demo.data-target. The inserts are performed correctly but when it comes to deploying activiti-examples.bar I encounter a SQL-exception telling me that a column named DBVERSION_ could not be found. Any ideas?


C:\activiti-5.0.alpha1\setup>ant db.create
Buildfile: C:\activiti-5.0.alpha1\setup\build.xml
     [echo] Activiti home = ..
     [echo] Activiti version = 5.0.alpha1

internal.classpath.libs:

db.create:
      [sql] Executing resource: org/activiti/db/create/activiti.mssql.create.sql
      [sql] 25 of 25 SQL statements executed successfully

BUILD SUCCESSFUL
Total time: 1 second
C:\activiti-5.0.alpha1\setup>ant db.demo.data
Buildfile: C:\activiti-5.0.alpha1\setup\build.xml
     [echo] Activiti home = ..
     [echo] Activiti version = 5.0.alpha1

internal.classpath.libs:

db.demo.data:
      [sql] Executing resource: C:\activiti-5.0.alpha1\setup\files\demo\mssql.data.sql
      [sql] 23 of 23 SQL statements executed successfully
[deploy-bar] Initializing process engine default
[deploy-bar] 24.05.2010 12:58:26 org.activiti.ProcessEngines initProcessEnginFromResource
[deploy-bar] INFO: initializing process engine for resource jar:file:/C:/activiti-5.0.alpha1/setup/build/activiti-cfg.jar!/activiti.cfg.xml
[deploy-bar] 24.05.2010 12:58:26 org.activiti.Configuration <init>
[deploy-bar] INFO: activiti version 5.0.alpha1
[deploy-bar] 24.05.2010 12:58:28 org.activiti.impl.ProcessEngineImpl <init>
[deploy-bar] INFO: ProcessEngine default created
[deploy-bar] 24.05.2010 12:58:28 org.activiti.ProcessEngines initProcessEnginFromResource
[deploy-bar] INFO: initialised process engine default
[deploy-bar] Starting to deploy 1 files
[deploy-bar] Handling file C:\activiti-5.0.alpha1\setup\build\activiti-examples.bar
[deploy-bar] deploying bar C:\activiti-5.0.alpha1\setup\build\activiti-examples.bar

BUILD FAILED
C:\activiti-5.0.alpha1\setup\build.xml:184: couldn't deploy bar C:\activiti-5.0.
alpha1\setup\build\activiti-examples.bar:
### Error updating database.  Cause: java.sql.SQLException: Ung³ltiger Spaltenname 'DBVERSION_'.
### The error may involve org.activiti.persistence.updateProperty-Inline
### The error occurred while setting parameters
### Cause: java.sql.SQLException: Ung³ltiger Spaltenname 'DBVERSION_'.

Total time: 4 seconds


[sebastian_s]

I mixed sql-scripts from the trunk with the released verson 5.0-alpha1. The column REV_ has been renamed to DBVERSION in trunk. That was the reason it was not working. This happends when you are too lazy to rebuild the project.