Post reply

Programmatically generate script for an SQl object

  • January 24, 2007 at 1:23 pm

    #685333

    DMO is deprecated - if you use DMO you won't be able to script objects in 2005 that don't exist in 2000, such as assemblies, etc.

    ---------------------------------------
    elsasoft.org

  • January 25, 2007 at 3:39 am

    #685462

    Well, I don't need to syncronize SQL 2000 and 2005 actually, and even if I need, I just need to syncronize common things like tables, procedures, functions, views, triggers. Mostly all of them are accessible via DMO.

    But thanks for the information, I'll keep it in mind (favorites:-)) in case I'll need something more flexible and cool in future.

    Thanks,

    Alex

  • January 25, 2007 at 7:40 am

    #685531

    ok, but there are things in even everyday objects that DMO won't know how to script properly, such as indexes with included columns, tables that use CLR types for a column, etc.  Just so you are aware.

    short story is you shouldn't do any NEW development using DMO, and it appears that you are.  DMO was included in 2005 only for back compat with legacy apps.  new code should not use it.

    ---------------------------------------
    elsasoft.org

  • January 25, 2007 at 8:00 am

    #685561

    Is there any better API for work with SQL server objects? Or COM?

    Thanks,

    Alex

  • January 25, 2007 at 8:01 am

    #685566

    2005 uses SMO.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • January 25, 2007 at 8:17 am

    #685578

    Yes.  Maybe I forgot to mention that scriptdb.exe uses SMO. 

    In fact, all of SSMS is built on top of SMO, just as EM was built on top of DMO.

    ---------------------------------------
    elsasoft.org

Viewing 6 posts - 16 through 21 (of 21 total)

You must be logged in to reply to this topic. Login to reply