InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 06:39:22 GMT20http://www.sqlservercentral.com/Forums/Topic1245048-1550-1.aspxI just noticed this 2008-2012 difference myself when looking at the max_worker_threads for the TSQL subsystem.I think sp_verify_subsystems must run whenever SQL agent starts. In 2008, it only inserts into the syssubsystems table if there are entries missing, so your modifications persist across restarts. In 2012, it truncates the table and re-inserts every time!All of the subsystems except Powershell are set to be multiples of the server's CPU count. The Powershell subsystem is hardcoded to 2, go figure. :hehe:Mon, 19 Nov 2012 15:01:45 GMTbgrecohttp://www.sqlservercentral.com/Forums/Topic1245048-1550-1.aspxI have been trying to change this in SQL 2012. Every time I change the value for PowerShell in the syssubsystems table when I restart the SQL agent it is set back to 2. SQL 2008R2 persisted this change. Anyone been able to change it in 2012?Wed, 07 Nov 2012 16:56:15 GMTJeffrey.Simmonshttp://www.sqlservercentral.com/Forums/Topic1245048-1550-1.aspxNo reason why you cant increase it. I've got it increased to 1/4 of my available cores on all servers. I dont expect to ever use that many but it allows more flexibility.Wed, 01 Feb 2012 08:09:03 GMTMysteryJimbohttp://www.sqlservercentral.com/Forums/Topic1245048-1550-1.aspxMy Sql Server Agent can only run two powershell jobsteps at one time which apparently is caused by the max_worker_threads setting:[font="Courier New"]SELECT subsystem, max_worker_threads FROM msdb.dbo.syssubsystemssubsystem max_worker_threadsTSQL 240ActiveScripting 120CmdExec 120Snapshot 1200LogReader 300Distribution 1200Merge 1200QueueReader 1200ANALYSISQUERY 1200ANALYSISCOMMAND 1200SSIS 1200PowerShell 2[/font]Why are so little PowerShell threads allowed compared to other subsystems? Is it save to set the value to say 10?Wed, 01 Feb 2012 06:56:27 GMTAlexander G.