Performance Concerns

Can SQL 7.0 reside on an existing server without
compromising the performance if other applications are
running?Bryanna,
Depends on the traffic of the OLTP.If its above average, then SQL7 may need
more resources like memory etc.
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Bryanna" <Bryalt@.aol.com> wrote in message
news:0cc101c351f6$14de3f20$a501280a@.phx.gbl...
> Can SQL 7.0 reside on an existing server without
> compromising the performance if other applications are
> running?|||"Bryanna" <Bryalt@.aol.com> wrote in message
news:0cc101c351f6$14de3f20$a501280a@.phx.gbl...
> Can SQL 7.0 reside on an existing server without
> compromising the performance if other applications are
> running?
Any time you add another running application to a machine it is going to
degrade performance somewhat, to what degree depends upon a lot of
variables.
1. Are you using a multiprocessor machine and delegating different
processors to different applications(processes), or are you using a single
processor machine?
2. The amount of RAM you have in your machine will help determine the
amount of impact running an additional application will have. The less RAM
you have the greater the impact on performance there will be when another
application is added.
3. Processor power also has a determining factor in this. The less
powerful the processor, the greater the impact of another application.
4. You didn't state what your database would be used for, i.e.
transactional or mainly data storage. You also didn't state how much usage
this database would get. A database that is accessed a couple of hundred
times a minute, compared to one that is accessed just a very few times a
minute also makes a difference.
5. What type, and how many hard disks are currently installed? Will you
add drives that will be dedicated to SQL 7, or will you attempt to run the
database on the same hard drive with other applications?
I'm sure I missed at least a couple of qualifiers as to how much an
installation of SQL 7 would degrade your current performance, but I guess to
sum it up I'd say, you didn't give anywhere near enough information to give
you an informed answer. With your given information I'd have to answer your
question by saying, yes and no.|||If you have enough CPU, memory, and I/O capacity on the system to handle the
additional load posed by SQL Server then the answer is yes. The
appropriateness of doing this is also highly dependent on what you are doing
with SQL Server. For lightweight use (low transaction rates) it is probably
ok, for heavy duty use you'll find that most DBAs prefer to have SQL Server
loaded onto its own system. That makes it far easier to tune, diagnose
problems, set the right management policies to guarantee database
availability and performance, set the right security policies, etc.
Hal Berenson, SQL Server MVP
True Mountain Group LLC
"Bryanna" <Bryalt@.aol.com> wrote in message
news:0cc101c351f6$14de3f20$a501280a@.phx.gbl...
> Can SQL 7.0 reside on an existing server without
> compromising the performance if other applications are
> running?

Perfomance tuning

Dear friends
We have one problem in our existing system.We are expecting some expert comment on this.We have one corebanking system back end as MS SQL server with IIS server.Our system is always very slow in the peak times of tranasactions.We are planning to optimize this with a short time plan .So pls give some suggestions that our DBA team can implement in a short time with SQL SERVER 2000

Thanks in Advance
Filson

A possible course of action is this:

Try to check your IIS's and SQL's processor during the peak times to see if the problem is with your SQL or IIS

If your problem is not in IIS:

Try to see if your sql server's processor is 100% or near. If it is, then your queries are probably too heavy - if it is not, then you possibly have locking problems.

Try to find if there are specific queries that are taking longer. You could use Sql Profiler for this, by specifying a duration minimum threshold for the events - for instance, only show queries that take more than 5 seconds (warning: this might deterioate even further your performance while the trace is active). After finding out the worse queries, try to understand why they are running slow - you could use SQL Query Analyzer for this, using the SP's execution plans.