Solution import on MSSQL

Classic Servoy
1

I am trying to import a Sybase solution into a new clean MSSQL 2005 server. Unfortunately, our i18n table is called ‘messages’. Because there is also a system view in MSSQL that has the very same name, the solotion import fails (the name ‘messages’ is already in use). However, I created the table manually with only a dummy column and restarted the import. Now, the columns get created by the import but then fails again whit this error:

[error] com.servoy.j2db.persistence.RepositoryException: java.sql.SQLException: Column names in each table must be unique. Column name ‘creator’ in table ‘messages’ is specified more than once.

So the import clearly bugs somewhere. I also tried denying the user to access te view, but since the user has dbowner privileges, this can’t be done. Renaming the table in the Sybase solution is also not really an option, since it is a core table of our framework which many customers already use. This would mean that future updates cannot be done. Anyone knows a way out?

2

The table name messages seems a reserved word on MSSQL (system view), rename your table messages, change solution settings accordingly, export your solution again. (Servoy does not require to name the table ‘messages’, it just needs table with the columns message_key,message_value and message_language columns)

3

Ruben,

Try filling in the appropriate schema in the server definition, it should make tables and views from system schema’s invisible to Servoy.
Check your db what the correct schema is, best guess for MSSQL is ‘dbo’.

Rob