October 29, 2007 at 10:04 am
A word of advice on your OnePoint database for MOM ... you need to switch it back to 'simple' recovery otherwise other MOM Jobs/Tasks will start complaining and causing you issues as the MOM database grows (and oh boy will it !).
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
October 29, 2007 at 10:22 am
Brandie Tarvin (10/29/2007)
I was under the impression, generally speaking, that the master db doesn't change that much or very often at all. That being the case, why would you need transaction log backups? In fact, why would you need a transaction log at all?
Master changes very little, but over time there will be changes (e.g. new logins, new DBs, etc). Like all databases, a transaction log is required so that the changes made can be rolled back if the transaction fails.
If you put master into Full Recovery, the transaction log will grow faster than the database probably will... A checkpoint is a logged operation, likewise backups. The log is needed, but Microsoft demands we keep master in Simple mode.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
October 29, 2007 at 10:40 am
Maybe I should have rephrased my previous post.
When I said "why would you need a transaction log at all", what I meant was, why would you need to hold onto transactions with a FULL or Bulk-Logged recovery mode. It's not like MASTER is a daily transactional database or anything. @=)
October 29, 2007 at 11:22 am
I have seen other places where it said that it was bad to switch the OnePoint database from Simple. Any ideas as to why it is not backing up when in the Simple mode?
October 29, 2007 at 12:33 pm
I've never used MOM or OnePoint before. Did you check your logs for specific error messages? Both SQL Server and OS logs?
October 29, 2007 at 3:29 pm
If your OnePoint databse is in 'simple' recovery mode you can cannot perform transaction log backups. If your full database backup is failing then the only thing that I can think of is that the drive/directory combination that your backup command is using eother does not existrs or the current credentials that the backup command is using does not have the authority to the drive/directory that you are targeting.
As for the OnePoint database being in 'simple' recovery mode, well when you install it in either MON 2000 or MOM 2005 that is the way that it is created.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
May 16, 2008 at 12:21 pm
So you means we can not do backup for transaction log?
I wonder why?
jchen
May 16, 2008 at 2:34 pm
To reiterate various comments already made in this thread: If the database is sent to simple recovery mode, no you cannot backup transaction logs. With respect to Onepoint (if that's what you're asking), it should be set to simple as that is how the vendor wants/needs it. If you have a database in full recovery mode, and it's a production database, I'd be sure I was doing transaction log backups at some interval otherwise your log (or disk) is going to fill up and all processing, for at least that database, will stop.
-- You can't be late until you show up.
Viewing 8 posts - 16 through 22 (of 22 total)
You must be logged in to reply to this topic. Login to reply