nespa
asked on
detach & reattach error logs?
the reason i'm asking this question is that i found (by dropping error logs) my DB size decreases substantially.
they're not needed immediately, but i'd like to save them (for now) and if possible reload into the database. is this even possible?
they're not needed immediately, but i'd like to save them (for now) and if possible reload into the database. is this even possible?
ASKER
yes, my question evolved a bit (and i noticed your response came in just after i accepted the last question - thanks for the last bit).
but i started a new question... here's my problem:
1) DB size is out of control. i'm performing many things including archival of unnecessary data.
2) When i delete the error logs it clears a lot of space
3) These error logs may be needed for viewing later... I'd like to analyze them when I have more time
4) However right now I want them *out* of the DB, to free space.
Is this possible? Is it possible to detach an error log, archive it (as files only), then re-attach it later & use sp_readerrorlog to read it? that would help me out.
but i started a new question... here's my problem:
1) DB size is out of control. i'm performing many things including archival of unnecessary data.
2) When i delete the error logs it clears a lot of space
3) These error logs may be needed for viewing later... I'd like to analyze them when I have more time
4) However right now I want them *out* of the DB, to free space.
Is this possible? Is it possible to detach an error log, archive it (as files only), then re-attach it later & use sp_readerrorlog to read it? that would help me out.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
excellent - great find. thanks!
You can set the option how soon you can recycle it, by default it is unlimited. In order to recycle it , right click on the SQLServerLog from EM, and set the option there