Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: javahollic on April 08, 2004, 05:31:24 am

Title: SQL server initial connection
Post by: javahollic on April 08, 2004, 05:31:24 am
Hi all,
Ive got EA4 demo and am running in Enterprise mode.  Im trying to create a project in SQLServer2000 but am not getting there.

I can use SQLclient toolls to browse DB and create tables using NT authority.

Ive tried using a named data source (results in Invalid ODBC Data Source, check ODBC configuration) and OLE DB Provider for SQL Server, resulting in "Invalid object name 'usys_system'".

Ive yet to find any magic SQL install script or other configuration information, does the schema get auto populated on first connect?

Anyone got the SQLServer connection working?  Is it an SQLServer2000 issue, there are no usys_ tables

Might ahve to try another db, anyone had success with MYSQL ?

Thanks,

andy
Title: Re: SQL server initial connection
Post by: Bruno.Cossi on April 08, 2004, 06:36:14 am
Hi Andy,

I am not sure if this is available only for the registered customers, but the SQL script for creating of the structure of the repository is available in the Corporate Resources section of sparxsystems website.

Bruno
Title: Re: SQL server initial connection
Post by: javahollic on April 08, 2004, 06:39:23 am
Hi, thanks for the reply, Ive found the SQL have installed the MySQL ODBC driver but am experiencing wierd errors surrounding SQL union calls.  To be insvestigated...
Title: Re: SQL server initial connection
Post by: Bruno.Cossi on April 08, 2004, 06:50:22 am
Well, there is really no visible difference to using DBMS based repository to the file based one. The .EAP file is nothing but an MS Access database, the same tables exist in it that would exist in the MS SQL Server (Oracle, MySQL, Sybase SQL....). EA works precisely in the same way regardless of where you store your model.

Bruno
Title: Re: SQL server initial connection
Post by: Stephen on April 08, 2004, 06:56:04 am
This does mean that you need to implement your own processes for creating new models and transferring details to them. Not an issue at all if only a small number of people do this, more of an issue in a distributed environment, but then your company will be used to having to handle it :)

Stephen
Title: Re: SQL server initial connection
Post by: Bruno.Cossi on April 08, 2004, 07:05:00 am
Hi,

I am thinking about this and really the only difference I see is the need to create a new database/schema for a new repository (which is really a task not unique to EA) and a need to create a new .EAP file and load it into the new schema once creating a new project. Is this what you meant? If it is, than I agree.
By the way, the loading to/from the DBMS repository could use a bit of improvement... ability to create a new project straight into the repository, based on a .EAP template, same way as when creating new .EAP file, would be nice...

Bruno
Title: Re: SQL server initial connection
Post by: javahollic on April 08, 2004, 07:31:55 am
Or even ONE database MULTIPLE projects, foreign key anyone? :)
Title: Re: SQL server initial connection
Post by: Stephen on April 08, 2004, 08:31:12 am
Bruno,

Yes - exactly what I was getting at.
Having written (to a just about useable level) the in-house utility to support mangling of models on SQL server its not as trivial as I thought when I started...

Stephen
Title: Re: SQL server initial connection
Post by: Bruno.Cossi on April 08, 2004, 10:40:32 am
Yes please! :-)
Often we need to keep projects separate and creating new Project Root Nodes in the same model just will not do.
And having to create new database/schema for every project is quite a bit of hassle, let alone the overhead and cost.

Bruno

Quote
Or even ONE database MULTIPLE projects, foreign key anyone? :)

Title: Re: SQL server initial connection
Post by: Bruno.Cossi on April 08, 2004, 10:41:38 am
Stephen,

agreed, completely. Let's hope SparxSystems read this and hear our cries!

Bruno

Quote
Bruno,

Yes - exactly what I was getting at.
Having written (to a just about useable level) the in-house utility to support mangling of models on SQL server its not as trivial as I thought when I started...

Stephen

Title: Re: SQL server initial connection
Post by: mchiuminatto on April 08, 2004, 11:57:29 am
And what if they add a version or date field to the tables so we can handle history for version control?

Or I'm asking too much?
Title: Re: SQL server initial connection
Post by: JimHinson on June 28, 2004, 01:12:56 pm
Quote
Hi Andy,

I am not sure if this is available only for the registered customers, but the SQL script for creating of the structure of the repository is available in the Corporate Resources section of sparxsystems website.

Bruno

I have the script.  I can see 'usys_system' in my local SQL2000 instance, yet I still get the error on connection.  Any ideas?

Thanks,


Jim
Title: Re: SQL server initial connection
Post by: thomaskilian on July 01, 2004, 05:02:06 pm
Just a guess: Did you check authorization?  Did you try accessing the database via ODBC (e.g. MSQRY)?
Title: Re: SQL server initial connection
Post by: Rob7795 on July 01, 2004, 08:46:24 pm
Quote
Hi, thanks for the reply, Ive found the SQL have installed the MySQL ODBC driver but am experiencing wierd errors surrounding SQL union calls.  To be insvestigated...


Hi Javaholic,

I've just gone through the MySQL install process and I'm getting what appears to be the same wierd sql/union problems when creating an element, opening a diagram, etc.  However, the database seems to be corect/intact.

Did you resolve you problem?  If so, can you post it?  Does anyone else have any suggestions?

Cheers, Rob. ???
Title: Re: SQL server initial connection
Post by: Tjerk on July 02, 2004, 01:22:19 am
Another guess, are you sure that you are using the correct versions of MySQL and also the ODBC driver (see somewhere on the corporate install pages of Sparx's site)? I also had some weird problems when I used older versions earlier.
Title: Re: SQL server initial connection
Post by: JimHinson on July 06, 2004, 05:48:24 am
I believe my issue was that I attempted to connect before creating a project (if so, seems like a better error message might be useful).  I've been able to create local projects and transfer them (Tools | Data Management | Data Transfer) to SQL, then connect.

Hope this helps,


Jim