Advice needed
From: Linchi Shea (linchi_shea_at_NOSPAMml.com)
Date: 12/29/03
- Next message: Hradesh: "Failed to start a new trace - SQL PROFILER"
- Previous message: Sherry: "Login exists in server and db, but doesn't exist???"
- In reply to: Don Grover: "Advice needed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 29 Dec 2003 12:42:26 -0800
Two methods:
1. Schedule a daily job on the server to run
sp_cycle_errorlog
2. Write a one-liner Perl as follows to filter out all the
login entry. This will singificantly reduce the file size
before viewing.
cmd>perl -e -p "s/^.+failed login.*$//i;" errorlog >
shorter_errorlog.txt
Linchi
>-----Original Message-----
>I have an sql server db on a remote dedicated server that
is open on
>internet, for remote report writing.
>The company that uses is it extremely large and well
known, due to this the
>sql server gets hammered by bogus logins.
>10,000+ of them a day,.
>Security wise its ok but the bloody error log files are
huge 27-48 mb.
>
>Because I logonto this server remotely atleast once a day
and check logs, I
>am finding it difficult to read them due to the size for
vieving log file
>in a TS session.
>
>How can I create 1 error log a day for 7 days then
recycle them, or atleast
>create them into more manageble sizes.
>Regards
>Don
>
>
>.
>
- Next message: Hradesh: "Failed to start a new trace - SQL PROFILER"
- Previous message: Sherry: "Login exists in server and db, but doesn't exist???"
- In reply to: Don Grover: "Advice needed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
