Post reply

the logfile for data xyz is full backup transaction log per the database to create space

  • May 25, 2004 at 6:06 am

    #359818

    it my client place problem is araised you have solution pls post immdtly

  • May 25, 2004 at 6:19 am

    #507628

    I assume the logfile is full for one of the databases. You haven't really posted much informaiton. You can try "backup transaction xyz with no_log" and then run a full backup of the database if that works.

  • May 25, 2004 at 6:36 am

    #507635

    You can run BACKUP LOG xyz WITH TRUNCATE_ONLY.

    That will free up some space. However, you need to find out why the log file is full.

    Are you doing backups? If not, you need to do this on a regular basis. You should at least be doing FULL backups. If your data is critical, you should be doing transaction log backups also. If it's not critical, you might consider changing the Recovery Mode to simple and only doing Full backups.

    Do you have the log file set to autogrow? If so, do you have it set to grow fast and large enough?

    The question you asked has been asked several times on this site (almost weekly). Please take the time and do a search. You'll find out lots of information about the transaction log being full and what to do about it. Especially, check in the forum for Backups.

    -SQLBill

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

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