Re: DB migration
- From: "Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 18 Jun 2008 07:38:54 -0500
To add to Erland's response, consider examining the execution plans of the parallel queries to see if index/query tuning is warranted. SQL Server will sometimes throw parallelism at a query to compensate for lack of useful indexes. I have seen cases where tuning eliminates parallelism and improves performance.
--
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"michael" <mharen@xxxxxxxxx> wrote in message news:944ac9e6-6751-43b6-81dc-54f025770485@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I just moved a SQL 2000 database to a new server (backup/restore).
This server is much beefier with respect to hardware.
The problem is that the system doesn't seem to be very fast at all. It
seems to be having issues with thread count. For example, I saw some
errors like this in my client apps:
"The query processor could not start the necessary thread resources
for parallel query execution."
Also, connections from SSMS occasionally timeout and running this
"query": "PRINT GETUTCDATE()" takes as long as 2 minutes to return the
current date.
What should I be looking for? What things should I check?
Is it possible the db is just taking IO hits like crazy as it spins up
(it's been up for about an hour now)?
Thanks!
.
- References:
- DB migration
- From: michael
- DB migration
- Prev by Date: Sifobo Enterprise Manager for SQL Server - Free Download
- Next by Date: SQL 2008 EULA and pricing
- Previous by thread: Re: DB migration
- Next by thread: bulk insert in clustered index table
- Index(es):
Relevant Pages
|
