I too am receiving very similar errors when using an area of interest file gdb polygon:
Data access failure, layer = Roads and Streets, error string = Underlying DBMS error [Microsoft SQL Server Native Client 10.0: The query processor could not start the necessary thread resources for parallel query execution.] [PROD.GIS.Streets]§TilesWorker: Data access failure, layer = Roads and Streets, error string = Could not access data for layer or table Roads and Streets during drawing
Failed to cache extent: 504171.875000 1009371.875000 538294.791667 1043494.791667 at scale 1200
Failed to cache extent: 606569.270833 992302.604167 623630.729167 1009364.062500 at scale 600
Data access failure, layer = Roads and Streets, error string = Underlying DBMS error [Microsoft SQL Server Native Client 10.0: The query processor could not start the necessary thread resources for parallel query execution.] [PROD.GIS.Streets]§TilesWorker: Data access failure, layer = Roads and Streets, error string = Could not access data for layer or table Roads and Streets during drawing
Failed to cache extent: 623635.937500 1043502.604167 640012.968249 1060564.062500 at scale 600
The index was either too large or too small.
However, as you can read the errors also involve TileWorker Process and Data access failures from SDE. Once I dumped our streets into a file gdb in a shared directory, no errors. I've been fighting data access failures since we went to 10.1.1 and sql geometry. We have spent hours tuning and testing, and yet the same errors keep cropping up. Our database server is connected to our san via failover nic cards, we have 16 cores on two cpus with 65gb ram.
This should not be happening!
Thanks
David Coley
Sarasota County
ArcServer Admin / Developer