🚀 go-pugleaf

In article <3oohfa$1om@usenet.INS.CWRU.Edu>,
Dhillip Anandam <dm235@cleveland.Freenet.Edu> wrote:
>
>I hope someone can help us.  We bought SQL server for NT for our project.
>At present, it hasn't gone into production because of the speed.  It is
>very slow even when we do updates to our database.  For example, for
>SQL server to update a table of 3500 entries, it takes more than 30 minutes.
>I was just wondering what we might be doing wrong.  Is there something
>we will have to do to get the system running faster?
>
>We are running the server on a Novell Network and using Named pipes to 
>access it.  The NT server has 128M RAm, 2 Pentium processors.  We got us 
>the fastest machine we could get.

Just a few guide lines:

 1) Put the table(s) you are updating and the log on different physical
    disk devices.  In general, if you can hear a lot of disk activity during
    the update process, you do not have an optimized database configuration.
    A rule of thumb is: the more disks, the better.  Use Performance Monitor
    to watch your %cpu and %disk activities.  When %disk goes down and %cpu
    goes up, you are doing the right thing regarding configuration.

 2) Remove indices from the table(s) being updated.  After the updates,
    rebuild the indices.  If the environment is online transaction processing,
    dropping the indices might not be possible.  For end-of-month processing,
    where your sql job is likely the only process touching the table, dropping
    the indices can be a BIG win.  I saw better than a x10 speed up!

Sounds like you have plenty of horsepower.  If you can't get your queries
working better, you might try posting some more specific information.  Like:

 1) Disk configuration.
 2) Database device definitions.
 3) Database/segment/table layout.
 4) Sample query.

Regards,
Mike