Post reply

Maintenance Plans Problem

  • August 31, 2006 at 3:16 am

    #60755

    Hi, hope someone care to sharing here. Thank you.

    I scheduled a job, but after start the job, it failed. The error capture as shown below:

    executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed [SQLSTATE 42000], error 22029. The step failed.

    Thanks a lot.

    Dunstan

     

  • August 31, 2006 at 6:49 am

    #657781

    The error you stated is pretty generic .

    Go to the job steps,select advanced and choose a file where the errors could be logged

    That could provide more information

  • September 1, 2006 at 10:16 am

    #658085

    A few questions first ...

    • Is the SQL Server Service using the LocalSystem account or a domain account ?
    • Is the SQL Agent Service using the LocalSystem account or a domain account ?
    • Have you removed or denied login to Builtin\Administrators ?

     

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • September 1, 2006 at 9:28 pm

    #658160

    Hi guys, thank a lot for the reply and sharing.

    I guess i found the actual issue, after the DB migrated, the server name was renamed and  the Builtin\Administrators name was renamed for security reason. Thus, Mainteinance Plan failed because using the old default account. To overcome this, i actually refer the job owner to sa after creating the job. Is that advisible to do that? Any other best practise?

    Beside that, Under what cicumtances we use "simple" and "full" mode backup? As i know, FULL mean including the transaction log. Right? Any impact on the DB if i change from simple to full?

    Thank you.

    Dunstan

  • September 3, 2006 at 6:32 am

    #658204

    my 2 cents...

    To answer your question about Simple and Full recovery model, I would say that it depends on business requirements. If your are looking for point in time recovery then Full recovery model is the way to go. Also, it depends on how much data you can loose in case of data/log drive failure. If recovery model is simple, you can recover the data and restore full backup to come back into the business. In full recovery model you can restore full back and then t-logs backup to reduce data lost.

     

     

  • September 3, 2006 at 8:15 am

    #658214

    Yes, thanks for the advice.

    Since Full + Tlogs more beneficial then simple, will stick on full backup, instead. (as there is no negative impact on the DB)

    Regard

    Dunstan

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

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