Problem Importing Database Schema from MSSQL

[David Brayley]

I'm evaluating Enterprise Architect for, among other things, data modeling.

I've tried to import the schema of an existing MS SQL Server (2000) database, but get no results.

The list of available tables in the dialog "Select Tables to Import" is empty.

I know that the ODBC connection itself is working, because the "Import DDL Schema from ODBC Data Source" dialog retrieves the name of the actual databae that I want to reverse engineer. I can import the database's stored procedures (though this operation does encounter some errors).

Can someone suggest what I might be doing wrong?

Thanks,
David Brayley

[«Midnight»]

OK Dave, I've tried this on my own without a problem. Here's what I did:

• Created a new package and diagram to import to. [The diagram is very important, and EA seems not to even try if you don't have one selected.
  
• Chose Project / Database Engineering / Import DB Schema from ODBC.
  
• Created a new data source with the SQL Server driver.
  
• Used integrated security in SQL Server when asked.
  
• Accepted the SQL Server login option for additional settings, and tested the connection when asked.
  
• Filled out the appropriate dialogs to indicate the catalog I was using - not the master catalog (you have to click the appropriate check box to get this working).
  
• Made sure I selected both diagram and package on the EA dialog when I returned.
  
• Clicked Import.
  

At this point I was presented the list, fully populated with the various entities as one would hope.

I am using the current build (789) of EA, with MS SQL Server 2000, SP 4 (or whatever the current revision level is). This is a SQL Server Developer installation rather than MSDE, but I have done the above with MSDE in the past (EA version 4.x or 5.x) without a hitch.

FWIW, I imported the EA schema from a model I have created in a SQL Server repository, excluding system tables, but including user stored procedures. EA balked on several of the stored procedures, claiming parsing errors, but finished the import just the same.

HTH,
(the other)David

[David Brayley]

Many thanks, other David, for looking at this. I've reviewed the steps you followed - essentially the same as the ones I followed, verified that I have all the same versions of software that you do (I do), and repeated the attempt to reverse engineer, with no change in results. I still see an empty list of tables to import.

To eliminate the possibility that this is a problem with my database, or my server, I tried importing the "Northwind" database from my local machine, and another application database from a server on our network. Results are the same.

At this point I'm not sure what question to ask, or where to look. Any suggestions?

[«Midnight»]

Did you select the Import as New Objects radio button checked? (I think this is the default, but who knows?)

There has got to be some step I missed. It'll be something I do automatically, so to me it is not so much obvious but unconcious. I do this often enough that it could be a problem.

Another question: did you have a package selected in the Project View tree? Once again the answer is almost certainly "yes," as it should be impossible to start the schema import process without doing so.

David

[David Brayley]

I've found that solution. I'd inadvertently entered a value in the "Schema/Owner" field - a value that did not correspond to any Schema or Owner in the database. Leaving this field empty did the trick.

Many thanks for the help!

[«Midnight»]

I am so glad you found it. I was really beginning to wonder what I'd forgotten about the process, and when it would surface here and trash my database.

So all is well, and you can get back to development. Excellent!

[thomaskilian]

I just found this one - hoorray! This saved my day