<p>2nd option definitely. Just do it with caution, test for performance early enough, check for slow queries, etc</p>
<p>Drupal can scale, you just have to think and understand what are you doing.</p>
<p>Why not D7?</p>
<p>JAnez</p>
<div class="gmail_quote">Dne 8. mar. 2012 15:57 je "Sam Cohen" <<a href="mailto:sam@samcohen.com">sam@samcohen.com</a>> napisal/-a:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi. <br><br>I was hoping for some advice. I recently took over an existing Drupal site for a nonprofit. <br><br>The client currently has a searchable database of a 115,000 records written in cold fusion in a separate database on a separate server. <br>
<br>They would like me to bring it into their Drupal 6 site or at least onto the same server. <br><br>I can do this in two ways:<br><br>1. As a custom module running off it's own db.<br><br>2. Or I can make it a content type and use Views for the interface. <br>
<br>My preference is to just use CCK/Views for maximum flexibility -- but I question whether or not it's wise to add a 115k records to the node and other tables and what type of impact this might have on overall site performance. (Any other downsides?)<br>
<br>Anyone have any advice/suggestions? If it was your project would you code it separately or use CCK/Views.<br><br>Thanks,<br>Sam<br clear="all"><br><br>Sam Cohen, Principal<br><a href="http://new-media-solutions.com" target="_blank">New Media Solutions</a><br>
Drupal Training & Services<br><a href="http://twitter.com/samcohen" target="_blank"></a><br><div style="display:inline"></div><div style="display:inline"></div><br>
</blockquote></div>