SSIS disk requirements

  • Hi all,

    we are going to do a PoC to use SSIS as our main ETL-system. For our SQL Server installations, we have a default disk template: system db, user db, tempdb, logs etc. each have dedicated volumes to maximize performance.

    I was wondering if the same applies for a dedicated SSIS. As most of its processing happens in memory, I would think you do not need this elaborate separation of disks, maybe only keep db and logs separate.

    I would appreciate your comments and recommandations.

  • Are you talking about running SSIS on a different server from the database engine? Bear in mind that if you do that, you'll need to buy a separate licence. But SSIS doesn't have any databases of its own. Any databases that it uses will have to live on a database engine instance somewhere. I've never run it separately myself, but if you do, I imagine the important things would be plenty of memory and a fast network connection.

    John

  • Hi John,

    each SSIS instance would in fact have its own database engine to store its databases, the catalog database etc.

  • So long as the server doesn't hold any of the databases that you'll be doing ETL on, then I'd agree that you're not likely to need a particularly sophisticated disk configuration. But don't take my word for it - make sure you test before it goes live!

    John

  • I agree with all of John's comments. Lots of memory and speed of connection to data sources would be high on the list.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • v-studios (3/18/2016)


    Hi John,

    each SSIS instance would in fact have its own database engine to store its databases, the catalog database etc.

    The catalogs databases are small and don't keep processing data. You don't need any disk configuration for them.

    Igor Micev,My blog: www.igormicev.com

  • Igor Micev (3/18/2016)


    v-studios (3/18/2016)


    Hi John,

    each SSIS instance would in fact have its own database engine to store its databases, the catalog database etc.

    The catalogs databases are small and don't keep processing data. You don't need any disk configuration for them.

    They keep logging information and can grow to be huge, actually. Attention should be paid to setting the Retention Period, Default Logging Level, Maximum Number of Versions Retained and Clean Logs Periodically properties appropriately.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • thank you all for your comments!

Viewing 8 posts - 1 through 7 (of 7 total)

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