SQL2000 is Unsupported Lang.!

[peace2008]

Hi,

I have sql2005 and EA 7.0.813 installed on my PC. I forward engineered from one of my DB schemes to a data model. Now I change a column in a table in sqlserver, then in EA press F7 to synchronize it with new changes. It says "SQL2000 is unsupported language...." :-?
Generally, I cannot reverse/forward engineer now.
Any idea is appreciate

[«Midnight»]

AFAIK the F7 shortcut invokes the synchronize code function. This is meant for source code (i.e. programming language) only. EA makes a distinction between a programming language and SQL dialect. This means you're out of luck for now.

There is a limited ability to change tables, at least from EA to the database - read the documentation first, as there are both limitations and cautions involved. I don't know if you can update individual tables from the DBMS side without importing the entire model again. Note that importing again will lose any custom updates you've made; the elements in the model would be removed and replaced, not updated.

Perhaps this will change in future, but not likely until a future version of EA.

HTH, David

[peace2008]

Thanks David for the immediate reply  

So far as I remember I was forward engineering to SQL2005 by generating DDL script and I was reverse engineering by importing the changes. Regarding reverse engineering, I remember the same experience as your comments but about forward engineering, I remember that it was working  :-/ Thought none of them is working now

[«Midnight»]

Is it possible you are using an older model? Around the time that EA 7.0 came out I had some problems where different versions of MS SQL were involved.

At least one set of problems originated from older project files. Those from before EA 7 did not have SQL Server 2005 as an option, since EA did not then provide explicit support. This caused some problems when I attached newer schemas, since EA did not understand the language. [To be more accurate, the EA engine would have understood, but the DBMS languages did not include any references.]

I was able to get around this by exporting the DBMS Language reference data from a new (empty) project and importing it over the older data in my earlier project.

I don't know if this would apply in your case though.

David