Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
rohans
Posting Yak Master
194 Posts |
 Posted - 2004-01-15 : 11:12:48
|
| I have a transaction log backup script scheduled by a job and it is currently filling up the application log of the server. How do I get around this? Here is the scriptbackup log db_name to disk='\\network_path' with init;All help appreciated. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-01-15 : 12:29:13
|
| What do you mean filling it up? One line will be written to the log each time the command is run. How is that a problem?You can specify -n and -e in the startup options for SQL Server. -n says not to use the App log, -e says to put the event in the SQL Server Error Log. I use the default, which is just -e. I want the events to go into both locations. The app log can be much faster for viewing than the error log if you are using EM.BTW, if you specify -n, it'll be for all events and not just the command that you posted. Tara |
 |
|
|
rohans
Posting Yak Master
194 Posts |
Posted - 2004-01-15 : 14:41:52
|
| What I am doing is backing up my transaction log every 20 minutes since I don't have replication on that box. so after a while the applog becomes full.All help appreciated. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-01-15 : 14:44:48
|
| Every 20 minutes isn't a lot, it's probably a little higher than average. We do ours every 15 minutes because that's the maximum amount of data loss that we can afford. Increase the size of your application log and have it overwrite events as needed.What does replication have to do with backups? Even on a system that has replication on it, you MUST still backup the database and logs.Tara |
|
|
|
|
|
|
backup filling app log