Post reply

ad-hoc backup of some DBs on disk G of mssql_db using A job

  • March 16, 2016 at 8:35 am

    #312115

    Hi

    every day we are taking ad-hoc backup on disk G of mssql_db for the following DBs

    •A_MSCRM

    •MSCRM_CONFIG

    •S1FLOW

    •S1B2FLOW

    •Connect

    I want to create a job to include all the backup's of fthe DBs on disk G of mssql_db in order to run in series ( when the First backup finishes the second will start).

    i will appreciate any help in order to do it ( using sp or script or anything else) and how can i monitor to see that everything is ok and all the backups were taken succesfully without problems.

    thanks in advance

  • March 16, 2016 at 8:40 am

    #1865625

    Here's one popular solution[/url].

    John

  • March 16, 2016 at 9:21 am

    #1865642

    ok

    is it posiible to use 5 different steps for each db and inside each step to use ( SQL Server 2012)

    BACKUP DATABASE [CONNECT] TO DISK = N'C:\Program Files\Microsoft SQL\...\MSSQL\Backup\CONNECT.bak'

    I an using differential backup

    is it correct ?

    also I want the .bak file to has the form " connect16032016" .. nameofDBtoday .. "DBnameDDMMYYYY"

    how can i do it

    thanks

  • March 16, 2016 at 9:35 pm

    #1865789

    georgheretis (3/16/2016)

    ok

    is it posiible to use 5 different steps for each db and inside each step to use ( SQL Server 2012)

    BACKUP DATABASE [CONNECT] TO DISK = N'C:\Program Files\Microsoft SQL\...\MSSQL\Backup\CONNECT.bak'

    I an using differential backup

    is it correct ?

    also I want the .bak file to has the form " connect16032016" .. nameofDBtoday .. "DBnameDDMMYYYY"

    how can i do it

    thanks

    This isn't a big task if you don't want to use Ola's good code.

    You could very easily create a "maintenance plan" for this small task and run the plan whenever you wanted with just a click or two. The key to "monitoring" would be to open the related job that get's created, open the step, select the "Advanced" tab on the left, and tell it to write to a file (you can overwrite or append). Either way, you can see what's been completed or in the progress of working by opening the file with something like NotePad, which does NOT lock the file. Something like WORD would lock the file and you DON'T want to do that.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

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

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