Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 635
  • Last Modified:

SQLVDI & max thread counts, limitation or issue w/SQL 2005 server native backups or ALL backups including image based?

the issue is with an eventID 1, Source=SQLVDI.   it appears that the scheduled backups 'may' be the root cause of the SQL error "Limit on 'Max worker threads' reached" which prevents further client connections.
there are approx 129 databases on a 32bit win2003R2 SP2.

we are trying to determine if SQLVDI is used solely by the native SQL server backup, ntbackup or even any 3rd party backup that does not used a SQL agent ans is image based.

we also have received feedback with the following as possible solutions:

1. stagger the backups by splitting them up into multiple jobs. though this approach is not feasible as we ontinue to add databases to the Sql Server and the maintnance of the staggering process will be difficult to keep track of.
2. move to 64-bit Sql Server where we'l' have upwards of 500 worker threads depending on the configuration
3. increase max worker threads setting for the current configuration. each worker thread will need 0.5 MB for its thread stack and by increasing this number we will be reducing memory from the buffer pool.

ultimately the objective is to prevent further SQLVDI event IDs and prevent "Limit on 'Max worker threads' reached" errors.

unless there is a major draw back, we will also consider switching from native SQL backups to an image based only backup.

SQL Server ver 9.0.4035

thank you.
0
rastafaray
Asked:
rastafaray
  • 5
  • 5
1 Solution
 
wittysloganCommented:
I know this is obscure but I once had problems with worker threads which came down to having exactly 613 jobs  on the server.  We cured this by adding a job so there were 614.  It is probably not this but just in case.
0
 
rastafarayAuthor Commented:
nice :)  TY for taking the time to respond wittyslogan
0
 
wittysloganCommented:
that problem with staggering.  You can set up a maintenance plan for a database.  At the end of the maintenenance plan you can then say "kick off another sql job"  It's a componenet on the maintenance plan gui.  
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
rastafarayAuthor Commented:
interesting TY wittyslogan.  may be the best workaround on this issue
0
 
rastafarayAuthor Commented:
the only problem is that we will need a wait time before the next SQL job is kicked off, will this be possible?
0
 
wittysloganCommented:
you could put a sql step which counts up to certain time.  

What would the delay be for?
0
 
rastafarayAuthor Commented:
just an update...

msft considers this as a known issue.  they are investigating possible solutions.

will keep you posted.

TY all
0
 
wittysloganCommented:
by the way if you need to delay use the waitfor syntax:

http://msdn.microsoft.com/en-us/library/ms187331(SQL.90).aspx

cheers
0
 
rastafarayAuthor Commented:
hi wittyslogan

not sure how waitfor can be applied to this Q.

ty for the feedback
0
 
wittysloganCommented:
Add a step to your job before the "start another sql job step" containing the wait for step.  That should do it.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now