Hi,

 I would like to have some advice on the settings to optimize the Server performance. I have a 7 Gig database (many ISAM files in 2 directory the biggest file is 1.2 gig).

My customer recently bought a Quad Core 2.6GHZ server with 8 Gig of RAM with SAS Hard Disk on a RADI 10 array. The server run on Windows 2003 64 Biits and will just be used for my database in PSQLV10 and Print Job spooling.

 My application  has a Maximum of 100 users (averarge 85 users). All the Users use Citrix to connect to the system. The Application do SQL query and all update  are done with Transactionnal function.

Any advice or comments on what should I change to enhance server performance will be greatly appreciated.

 Thank you very much

 Marc Gauthier

What's your performance like now?  

What do you want it to be?  

Where do you see the slowest performance?

Using the PSQLv10 64-bit engine is greatly preferred in this environment.  With that size of database, I would recommend setting up 5GB to 6GB of L1 database cache and disabling the L2 cache and System Cache.  This will keep a majority of the data in memory and in thew working set at all times, and it should positively fly.

Of course, raw I/O performance is only half of this.  With SQL apps, you need to have well-designed SQL queries (using indices), and well-designed database (providing proper indices for the queries to use).  You may wish to look at this one query at a time with the Query Plan Viewer and make sure that the queries are being optimized as you expect.
 

1-Right now the performance is good but we are not in production yet. The current server has some slowdown, since we had SATA drive we think that was part of the issue and teh fact that my customer has quadruple is user base.

2- Has fast as possible

3- Big batch job and some  SQL Queries

Best Regards,

Marc

BtrieveBill:

Using the PSQLv10 64-bit engine is greatly preferred in this environment.  With that size of database, I would recommend setting up 5GB to 6GB of L1 database cache and disabling the L2 cache and System Cache.  This will keep a majority of the data in memory and in thew working set at all times, and it should positively fly.

Of course, raw I/O performance is only half of this.  With SQL apps, you need to have well-designed SQL queries (using indices), and well-designed database (providing proper indices for the queries to use).  You may wish to look at this one query at a time with the Query Plan Viewer and make sure that the queries are being optimized as you expect.
 

 Thanks Bill I will try this the cache. I will also take a look at my sql query with the Query Plan.

Thanks Again.

 Marc