DB Schema of EA

[Centurio]

Hi fellows,

I've written a automation script for EA. For not disturbing the workshop I prepared a Project Transfer to work on a .eap file, workshop is running MS-SQL-Server.

I used the table q_connectors and when I tried the script very first time on the workshop q_connectors was not found.

Seems, EA-database Schema depends on the underlying database system. WHAT THAT NONSENS?

 

Centurio

[beginner]

Hail Centurio!
You dumb user shall not know anything about the underlying database structure. You shall use the API. Burned fingers are to blame to yourself.

Write that a 100 times: You shall not bypass the API.

b(rian)

[Centurio]

Yes Sir, Right Sir, as you like
(when you will provide a fine API ...)

[Geert Bellekens]

Centurio,

Are you sure the q_connectors is a standard EA table?
In my databases I only see t_connector, and no such thing as q_connectors.
Maybe somebody at your firm has been messing around with the EA database, and has added this q_connectors table?

That, or you are using a very old database schema, and you might consider upgrading the schema. There have been quite some enhancements to the schema recently (in terms of performance: indexes and stuff)

Geert

[Centurio]

Hi Geert,

thank you for your answer. Maybe, I'm using weak tools, but anyway, in the meantime I was creating a workaround using t_connectors.
How can a Schema-Upgrade be performed?

Greetings
Centurio

[Geert Bellekens]

We did an upgrade when we upgraded from SQL2005 to SQL2008
The steps where:

- download the db creation script from sparx website
- run db creation script on new server
- run project tranfer from within EA (source = SQL2005, target = SQL2008)
- make old database unreachable for everyone but the admin, and connect to new database.

There is also an update script available for download, but at the time I tested it (about 6 months ago) there were still some bugs in that script. I reported the errors, and Sparx claimed to have fixed them. I didn't bother to test it anymore.

Geert