Hello - i did post this ealier but i think it went into the wrong section of the web site so apologies if your re-reading this/.
We use backup 7 to do nightly backups (1am) and we backup the transaction logs every 10 mins on certain databases.
When ever i get a cpu alert (resource can be anywhere between 80 -100%) i look at the most costly cpu proccess and it is always the SQBCoresercvice which is taking all of the cpu.
I have checked the log backups from the point in time where the cpu max's out using the msdb..backupset and the results returned dont show any exdroindary large transaction log backups - just the same size on average as the rest of the day.
We also have transactional replication - could this be the smoking gun ?
Users are starting to complain of unresponsive systems whilst this cpu is pegged at 80 - 100%
Any ideas ?
We use backup 7 to do nightly backups (1am) and we backup the transaction logs every 10 mins on certain databases.
When ever i get a cpu alert (resource can be anywhere between 80 -100%) i look at the most costly cpu proccess and it is always the SQBCoresercvice which is taking all of the cpu.
I have checked the log backups from the point in time where the cpu max's out using the msdb..backupset and the results returned dont show any exdroindary large transaction log backups - just the same size on average as the rest of the day.
We also have transactional replication - could this be the smoking gun ?
Users are starting to complain of unresponsive systems whilst this cpu is pegged at 80 - 100%
Any ideas ?