It's a small record set. As long as the queries are designed properly
and it's indexed you'll be fine with a shared SQL Server - unless you
mean *really* intensive. The size of the database isn't really as
significant as the number of concurrent accesses.
Nick
-----Original Message-----
From: Brook Davies [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 05, 2001 7:56 PM
To: CF-Talk
Subject: SQL SERVER Usage Question
I have a client who's new site will have a 20,000 record song catalog. The
site is search intensive. Is this a small record set? Should I consider a
dedicated SQl Server or can I use a shared SQL server without a huge impact
on the SQL Server usage. The SQL Server is 7,0, 1 gig of ram and a dual 550
processor with RAID 1.
Thanks for the advise, I realize the question is a little vague.....
**********************************************************************
Information in this email is confidential and may be privileged.
It is intended for the addressee only. If you have received it in error,
please notify the sender immediately and delete it from your system.
You should not otherwise copy it, retransmit it or use or disclose its
contents to anyone.
Thank you for your co-operation.
**********************************************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
