SSMS Scripting out tables/indexes is useless

  • I have a number of partitioned tables and indexes, on various filegroups.

    In SSMS i scripted the objects out but scripts do not mention partition scheme or the relivant filegroup.

    Technically, this means that SSMS is spitting out an incorrect script as the script is not the script to recreate the object in question.

    Why bother even including the functionality if its this messed up?

    Outside of writing dynamic sql to create my tables and indexes based on metadata, have I any other Quick Win Options?

  • Winston i think it's a scripting option that is turned off by default;

    if you change these settings, do you get the script you are expecting?

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • There are a lot of scripting problems in SSMS, some are pretty dangerous if you use replication or have large tables.

    Including them in the application is useful and allows for speedy learning of the basics as well as quick shortcuts for the experienced.

    I never simply run a command through SSMS. I always script the action first as a precaution, edit as necessary and run.

  • Lowell (10/11/2011)


    Winston i think it's a scripting option that is turned off by default;

    if you change these settings, do you get the script you are expecting?

    This is perfect ( well, it looks perfect on initial inspection!). il play with this and see if it is accurate in its scripting, at least for my purposes.

    Thanks!

Viewing 4 posts - 1 through 3 (of 3 total)

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