Rank: Guest
Groups: Guest
Joined: 9/17/2007
Posts: 11,670
Points: -1,200
|
Date parsed: 21/10/2007 00:13:21
Date: Sun, 21 Oct 2007 07:13:21 -0700
SQL Server uses multiple processors by default, though it gets into details
I don't know.
Check 2005 BOL for the following page:
(max degree of parallelism)
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/4445b385-5992-4d2d-bfd7-9e8ad869c5c9.htm
Also:
RECONFIGURE;
and
EXEC sp_configure;
"Sajjad" <spirahesh@gmail.com> wrote in message
news:1192975398.771008.300920@e34g2000pro.googlegroups.com...
> Hi,
>
> We have a SQL Server 2005 Enterprise database running on a HP ML 370
> Server with 4 processors, which has a Windows .Net 2003 as OS. But at
> a time process of Sql Server running on a single processor of the
> server.
> 1. Has Sql Server 2005 this capability that could run on Multi
> Processors? Could we obtain to this aim by configuring Sql Server? or
> can we achieve it by configuring Operating System?
> 2. Our database grows so fast,that We suggest that we encounter with
> response time delay problem after a while. Which Administration
> technique (like Indexing, clustering, moving old data to a secondary
> DB, ... ) is better for maintaining our database.
>
> Thanks in advanced.
>
> Regards
> Sajjad
>
|
Rank: Guest
Groups: Guest
Joined: 9/17/2007
Posts: 11,670
Points: -1,200
|
Date parsed: 21/10/2007 05:17:19
Date: Sun, 21 Oct 2007 10:17:19 -0500
> 1. Has Sql Server 2005 this capability that could run on Multi
> Processors? Could we obtain to this aim by configuring Sql Server? or
> can we achieve it by configuring Operating System?
SQL Server 2005 Enterprise Edition will use all available available
processors by default. However, a single query will use multiple processors
only with a parallel query plan. Only some types of queries will benefit
form parallelism.
> 2. Our database grows so fast,that We suggest that we encounter with
> response time delay problem after a while. Which Administration
> technique (like Indexing, clustering, moving old data to a secondary
> DB, ... ) is better for maintaining our database.
Most performance gains come from database and application design, query
tuning and indexing. Clustering is mostly for availability. Moving old
data to another database isn't usually needed to improve performance because
appropriate indexes can provide good response time regardless of table size.
Large tables (many millions or billions or rows) tables can be difficult to
manage. Partitioning can improve manageability without needing to move old
data elsewhere.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Sajjad" <spirahesh@gmail.com> wrote in message
news:1192975398.771008.300920@e34g2000pro.googlegroups.com...
> Hi,
>
> We have a SQL Server 2005 Enterprise database running on a HP ML 370
> Server with 4 processors, which has a Windows .Net 2003 as OS. But at
> a time process of Sql Server running on a single processor of the
> server.
> 1. Has Sql Server 2005 this capability that could run on Multi
> Processors? Could we obtain to this aim by configuring Sql Server? or
> can we achieve it by configuring Operating System?
> 2. Our database grows so fast,that We suggest that we encounter with
> response time delay problem after a while. Which Administration
> technique (like Indexing, clustering, moving old data to a secondary
> DB, ... ) is better for maintaining our database.
>
> Thanks in advanced.
>
> Regards
> Sajjad
>
|
Rank: Guest
Groups: Guest
Joined: 9/17/2007
Posts: 11,670
Points: -1,200
|
Date parsed: 21/10/2007 14:03:18
Date: Sun, 21 Oct 2007 14:03:18 -0000
Hi,
We have a SQL Server 2005 Enterprise database running on a HP ML 370
Server with 4 processors, which has a Windows .Net 2003 as OS. But at
a time process of Sql Server running on a single processor of the
server.
1. Has Sql Server 2005 this capability that could run on Multi
Processors? Could we obtain to this aim by configuring Sql Server? or
can we achieve it by configuring Operating System?
2. Our database grows so fast,that We suggest that we encounter with
response time delay problem after a while. Which Administration
technique (like Indexing, clustering, moving old data to a secondary
DB, ... ) is better for maintaining our database.
Thanks in advanced.
Regards
Sajjad
|
