SSIS! Challenge for a new package -- SQL Serve 2008R2

  • Folks,

    I think it will be beneficial to all to create a generic administrative backup SSIS which must be able to:

    1. Take a type of backup from a configuration file and according to that make a full, diff or tran backup.

    2. Must be able to have a list of included and excluded databases to backup from another configuration file

    3. The third configuration file must be able to pass-on a backup path as a parameter.

    We can use databases test1, test2, test3 as an example

    Really appreciate your help and interest. I do believe that many people here will get a good educational and practical kick from it.

    if one wants it.. one will justify it.

  • If you think it would be so beneficial why don't you create one and post for all to see.

    Why don't you try it, and if you get stuck somewhere let us know where and we can help you get thru it.

    Disguising your work as a "Challenge" for us to do will not teach you anything.

    A google search turned up this

    http://www.maarty.cz/?p=185

  • a really awsome TSQL based stored procedure already exists for handling database backups is part of the suite here :

    http://ola.hallengren.com/

    that solution is peer reviewed and award winning, and is deployed in a lot of production servers.

    if you wnated to, you could always call it via SSIS if that was your favorite tool.

    or you could re0invent the wheel, i guess.

    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!

  • Why 3 separate config files? Why not 1 xml config with:

    database name

    include or exclude (have to figure out what to do if you find a db on the server not in your config)

    backup type

    time window

    backup file path

    That way you could have full backups for a db during one time window and log backups at other time windows. The package would wake up every x minutes and figure out which backups it needed to do based on the time of day.

    But all in all, I don't see why this would be better than having any of the available generic backup scripts floating around the community running on a set schedule.

    What problem is this really solving?


    And then again, I might be wrong ...
    David Webb

  • one file could be a lot better option but then I think I will get more flexibility if I will create several.

    ... and yes.. I am working on creating one.

    if one wants it.. one will justify it.

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

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