September 7, 2013 at 8:31 am
is litespeed one of the causes of high cpu??
September 19, 2013 at 5:59 am
the default within Litespeed is to parallelise across all available CPUs. Using the @affinity and @throttle parameters you are able to specify which processors the backup uses and the max CPU %
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 24, 2013 at 3:00 am
Perry Whittle (9/19/2013)
Using the @affinity and @throttle parameters you are able to specify which processors the backup uses and the max CPU %
Can we take help of Resource Governor in Sql 2008 for this ?
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
September 26, 2013 at 6:43 am
Bhuvnesh (9/24/2013)
Perry Whittle (9/19/2013)
Using the @affinity and @throttle parameters you are able to specify which processors the backup uses and the max CPU %Can we take help of Resource Governor in Sql 2008 for this ?
If you're using SQL 2008, I would suggest using native backup compression over LiteSpeed. Litespeed has it's own issues when running concurrent backup processes that native compression doesn't suffer from.
[font="Courier New"]sqlmunkee[/font]
[font="Courier New"]Bringing joy and happiness via SQL Server since 1998[/font]
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply