Results 1 to 11 of 11
  1. #1
    Join Date
    Aug 2003
    Posts
    5

    Unanswered: Call for Gurus!!!. converting msSQl schema into standard format (DDL, XML)

    Hi,

    I am wondering if any of the DB Gurus out there help me finding a way to export mssql SCHEMA (not the actual data) into any standard language, like DDL, XML. At this point converting to XML would be the ideal but I am open to DDL format also.

    I would love to hear any feedback about "If this is even possible
    or not ?".

    thanks,
    tinki

  2. #2
    Join Date
    Aug 2003
    Posts
    5

    little clarification

    Schema can be in a SQL script form. So, ideally this tool that
    I am looking for will convery this SQL script info to DDL or
    XML.


    Thanks in advance,
    Tinki

  3. #3
    Join Date
    Feb 2002
    Location
    Houston, TX
    Posts
    809
    Have you tried Enterprise Manager?
    Paul Young
    (Knowledge is power! Get some!)

  4. #4
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    DDL, or Data Definition Language, is RDBMS-specific, meaning that it is not like COBOL, VBScript, or XML. DDL for Oracle will look differently than DDL for Sybase for the same set of tables, while certain objects in Oracle will not even be found in Sybase. XML on the other hand is a standard.

    Try DBArtisan from Embarcadero. Even though it only has an option "Extract Data as XML", it also allows you to generate the schema portion of your data.

  5. #5
    Join Date
    Feb 2002
    Location
    Houston, TX
    Posts
    809
    mySQL and SQL Server have very similar DDLs
    Paul Young
    (Knowledge is power! Get some!)

  6. #6
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    I'm glad

  7. #7
    Join Date
    Aug 2003
    Posts
    5
    Originally posted by Paul Young
    Have you tried Enterprise Manager?
    yes, I have tried Enterprise manager. It lets me export data to SQL script (which is very database specific). what I am looking at something
    which can convert this SQL script to something more wodely accepted as a general standard so that my rest of the code does not get too
    much database dependent.

    tinki

  8. #8
    Join Date
    Aug 2003
    Posts
    5
    Originally posted by rdjabarov
    DDL, or Data Definition Language, is RDBMS-specific, meaning that it is not like COBOL, VBScript, or XML. DDL for Oracle will look differently than DDL for Sybase for the same set of tables, while certain objects in Oracle will not even be found in Sybase. XML on the other hand is a standard.

    Try DBArtisan from Embarcadero. Even though it only has an option "Extract Data as XML", it also allows you to generate the schema portion of your data.
    thanks rdjabarov, I will try DBArtisan.

    I have tried XMLSPY but it couldn't get to export schema. It was exporting only the data.

    tinki.

  9. #9
    Join Date
    Feb 2002
    Location
    Houston, TX
    Posts
    809
    Originally posted by rdjabarov
    I'm glad
    I'm glad your glad!

    Should have read tinki's post a little closer, thought he wanted a MSSQL to MYSQL convertion.
    Paul Young
    (Knowledge is power! Get some!)

  10. #10
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    DBArtisan is somewhat pricy, but a must-have tool. Also does lots of other things.

  11. #11
    Join Date
    Aug 2003
    Location
    Delft, The Netherlands (EU)
    Posts
    447
    Originally posted by tinki
    what I am looking at something which can convert this SQL script to something more wodely accepted as a general standard so that my rest of the code does not get too much database dependent.
    tinki
    Are you actually looking for a db-independent db structure, rather than exporting your current db structure? Then, you should take these recommendations into account:

    1) use short (table & field) identifiers (Informix 7, for instance, has a maximum length of 18, and Oracle 40)
    2) use just characters, digits and the underscore for your identifiers
    3) use just ANSI SQL data types, and not, for example, BOOLEAN (BIT)
    ....
    I'm sure that the real gurus in this forum can easely enhance this list.

    However, using a data model with no db-specific properties makes it easy to build a db-independent application, with or without a middleware encapsulating db-specific properties.
    Make everything as simple as possible, but not simpler! - A. Einstein
    DB Problems? DB Explorer, BTrieve Re-engineering, DB Conversions & ETL? Conversion Tool

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •