Re: system setup survey

Given that it's static data, you'll find that SQL Server 7.0 and Windows 2000/Visual Studio 6 will allow you to wrote a COM+ back-end which allows you to load balance across a number of (identical) SQL Servers. For a dynamic data store with a similar query count (but allowing updates, inserts, deletes, etc...) you'd probably be better off with a UNIX based RDBMS - maybe DB2 or Oracle.

Before I could give any serious advice though, I'd have to know roughly what kind of system you are looking to implement here. Is the static datastore ever updated? How regularly? What kind of data volume will be affected in your refresh? Will you be doing refreshes online? Or will you refresh the database off-line, dump it and then load into the online environment? Some DBMS's have faster dump and load but have poor transaction throughput. Others are super-fast transactionally but dodgy on dump/load.

Jeremy Huppatz
Database Administrator
Macquarie Bank Limited
jhuppatz_at_macquarie.com.au
Neil Pike <100577.553_at_compuserve.com> wrote in message ...
>Garrett - SQL 7 could easily cope with this sort of figure assuming
>transactions are "small".
>
> Neil Pike MVP/MCSE. Protech Computing Ltd
> (Please post ALL replies to the newsgroup only unless indicated otherwise)
> For SQL FAQ entries see
> http://go.compuserve.com/sqlserver (library 1) - latest stuff is always
here
> www.ntfaq.com/sql.html
> http://www.swynk.com/faq/sql/sqlserverfaq.asp
>
>
Received on Mon Jul 26 1999 - 19:23:56 CDT