v15 - Rev. Eng. SQL Server 2008 DB (via Database Builder)

[Paolo F Cantoni]

We've had success reverse engineering several SQL Server databases which are later than SQL Server 2012 (using the SQL Server 2012 model and Database Builder).

We reverse-engineered a new DB and found that the View, Function and Constraint definitions didn't import (the objects did, but no data in the appropriate tag).  Investigating, we found that this was a very old SQL Server 2008 DB.

Is there anything we can do to get it to import the definitions correctly?  We've tried using the SQL Server 2008 model - to no avail! 

TIA,
Paolo

[Modesto Vega]

Strange, very strange. v13 had not problem with SQL Server 2008 database, I am looking at a repository with several SQL Server 2008 reversed engineered databases (with views, functions and stored procedures).

The only 'weird' thing is that they were reversed engineered as SQL Server 2012 databases and I don't know why we did this.

One really stupid questions, which I am almost embarrassed to ask: have all schemas and object types being selected?

One observation, for SQL Server SQL Native connections are better than ODBC connections.

[Paolo F Cantoni]

Strange, very strange. v13 had no problem with SQL Server 2008 database, I am looking at a repository with several SQL Server 2008 reversed engineered databases (with views, functions and stored procedures).

The only 'weird' thing is that they were reversed engineered as SQL Server 2012 databases and I don't know why we did this.

One really stupid questions, which I am almost embarrassed to ask: have all schemas and object types being selected?

One observation, for SQL Server, SQL Native connections are better than ODBC connections.

I tried the SQL Server 2012 model first (like you, we just kept using it).

I'll see if I can get a direct connection on Monday.

[Edit: you can only import to the Database builder via an ODBC source.]

Thanks,
Palo

[Modesto Vega]

[SNIP]
[Edit: you can only import to the Database builder via an ODBC source.]

You can most definitely reverse engineer SQL Server database with the SQL Server Native Client, we do it regularly with version 13 and 14.

Having said this, please keep in mind that the I think it needs to be installed.

[Geert Bellekens]

I think you are both correct.

You need to setup a DSN via the ODBC data sources dialog, but when creating that DSN you can choose for different drivers.
There might be a difference if you depending on what you choose to connect to the database.
I have these options for SQL Server:

- ODBC driver 11 for SQL Server
- ODBC driver 13 for SQL Server
- SQL Server
- SQL Server Native Client 11.0

Geert

[Paolo F Cantoni]

Hi Geert & Modesto,

This morning I discovered that I don't have access to the metadata.  The Service Account I was using only gets me the actual data (for import into our DW).

Trying to access the metadata directly via SSMS (thanks, Modesto) showed the issue.  I'm now waiting to see if I can get permission to access the metadata.

Paolo