Hi,
I am a DBA for SQL server and I have a poduct to be tested for performance
with backend MSSQL Server 2005 developer edition. I have a machine of 8CPU's
and the senario is
the dataserver has to function for some big computations and data processing.
application is on .Net c# code also will be loaded on the same machine,
should also be scaleable with multiple users working on the app. and database
access.
My question is
1) Is there a guodeline for spliting the CPU's with MSSQL server and OS ( OS
and App)
2) Are any documented(cases) white papers on the same(resourse charing
between OS and sql server).
Please share you experiencies.
Thanks,
fellow DBA.Hi
"Krish" wrote:
> Hi,
> I am a DBA for SQL server and I have a poduct to be tested for performance
> with backend MSSQL Server 2005 developer edition. I have a machine of 8CPU's
> and the senario is
> the dataserver has to function for some big computations and data processing.
> application is on .Net c# code also will be loaded on the same machine,
> should also be scaleable with multiple users working on the app. and database
> access.
> My question is
> 1) Is there a guodeline for spliting the CPU's with MSSQL server and OS ( OS
> and App)
> 2) Are any documented(cases) white papers on the same(resourse charing
> between OS and sql server).
> Please share you experiencies.
> Thanks,
> fellow DBA.
I don't know of any white papers, these things are not recommend to be on
the same machine; a general value would only be a starting point anyhow. You
should decide the configuration from the results of your load testing and
cover as many hardware combinations as possible to get the best results.
You can not use Developer Edition for a production system, if the hardware
you are testing on is not the same as the destination server you may only
have a general guideline to performance.
John
No comments:
Post a Comment