Post reply

Transactional Replication - Not enough storage space to complete this job

  • January 15, 2004 at 5:09 am

    #84349

    Hi There

    We currently have transactional replication (pull on demand) set up on one of our databases. When we try and run the job to pull the data down we get an error message saying there is not enough storage space to complete this job.

    There is over plenty of space available both on the server and the laptop pulling the data.

    All of the databases have, grow automatically selected and unrestricted file growth (including msdb database)

    There's plenty of swap space available (we increased this just to be on the safe side and it made no difference)

    All ideas gratefully appreciated!

  • January 15, 2004 at 7:29 am

    #490195

    if you are first sincronizing with the snapshot, also check space in the system disk (where your temp folder is) because SQL first extract every snapshot file into that folder.

  • January 15, 2004 at 7:52 am

    #490198

    we've been successfully replicating over the network here for a while now and this is just a pull of a couple of days transactions. There's sufficient space on both the publisher and the subscriber and all databases are set to automatically grow.

    One thing to note is that as when we kick of the pull subscription we never see any evidence on the publisher that it has makes any kind of a connection to the publisher.

    Thanks for your help

     

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

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