Very Computer

I'm working on a system that will have very high transaction loads (upwards
of 300 transactions per second).  I have two questions associated with this
development.

1.)  Can SQL Server 7.0 handles that kind of load

2.)  Can I make certain tables in SQL Server 7.0 memory resident to reduce
seek time?  What are the pro's and con's of this method?

Dylan

Hi Dylan, look up DBCC pintable( database_id, table_id) in BOL. BOL includes
the Pro's and Con's as well.

regards
jensk

Quote:> I'm working on a system that will have very high transaction loads
(upwards
> of 300 transactions per second).  I have two questions associated with
this
> development.

> 1.)  Can SQL Server 7.0 handles that kind of load

> 2.)  Can I make certain tables in SQL Server 7.0 memory resident to reduce
> seek time?  What are the pro's and con's of this method?

> Dylan

It's actually recommended that you use sp_tableoption with the PINTABLE
option. Look up sp_tableoption for details. This proc actually calls the
DBCC, but sp's are always preferred over dbccs. The DBCC is not guaranteed
to stick around in the future.

HTH

--
------------------------------------
Kalen Delaney
MCSE, SQL Server MCT, MVP
www.InsideSQLServer.com

Feed Someone for Free Today:
     www.TheHungerSite.com

It's actually recommended that you use sp_tableoption with the PINTABLE
option. Look up sp_tableoption for details. This proc actually calls the
DBCC, but sp's are always preferred over dbccs. The DBCC is not guaranteed
to stick around in the future.

HTH

--
------------------------------------
Kalen Delaney
MCSE, SQL Server MCT, MVP
www.InsideSQLServer.com

Feed Someone for Free Today:
     www.TheHungerSite.com