Thanks everyone. This was all really helpful. <br><br>Sorry if I wasn't clear. I'm not look for a "how to," as much as any concerns I need to consider on doing this in Drupal verses outside Drupal. Sounds like the main consideration is search performance, but otherwise, adding that many nodes to a site shouldn't have any negative consequences?<br>
<br>Sam<br><br><br clear="all">Sam Cohen, Principal<br><a href="http://new-media-solutions.com" target="_blank">New Media Solutions</a><br>Drupal Training & Services<br><i><a href="http://new-media-solutions.com/drupal-training" target="_blank">New Courses Starting Soon</a></i><br>
<a href="http://twitter.com/samcohen" target="_blank"></a><br><div style="display:inline"></div><div style="display:inline"></div><br>
<br><br><div class="gmail_quote">On Tue, May 1, 2012 at 9:30 AM, Steve Purkiss <span dir="ltr"><<a href="mailto:steve@purkiss.com" target="_blank">steve@purkiss.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You could always try a support channel on IRC:<br>
<a href="http://drupal.org/irc" target="_blank">http://drupal.org/irc</a><br>
<br>
In the mean time, check out:<br>
<br>
<a href="http://drupal.org/project/migrate" target="_blank">http://drupal.org/project/migrate</a><br>
<br>
...and...<br>
<br>
<a href="http://drupal.org/project/feeds" target="_blank">http://drupal.org/project/feeds</a><br>
<div class="HOEnZb"><div class="h5"><br>
On 1 May 2012 14:25, Sam Cohen <<a href="mailto:sam@samcohen.com">sam@samcohen.com</a>> wrote:<br>
> This list has sure gone quiet lately. Is everyone just so busy with work?<br>
><br>
> (Sorry if this isn't the place to ask this. If anyone knows a better place,<br>
> please advise. )<br>
><br>
> A client of mine with a Drupal site I inherited wants to bring in a very<br>
> large database into their site. It's basically over 200,000<br>
> genealogical/cemetery records that need to be searchable by users. I'm<br>
> struggling over whether to do it (1) as a custom module, with it's own<br>
> separate database or (2) to do it with views/content type and node import.<br>
> The client also needs to be able to edit the records through the site.<br>
><br>
> The latter approach would be quicker to set up, but I worry that it would<br>
> bloat the site, potentially cause performance issues, and perhaps other<br>
> problems I'm not thinking about.<br>
><br>
> It's a D6 site for a relatively small nonprofit without a lot of traffic.<br>
><br>
> How would you handle it? Custom module or content type/Views?<br>
><br>
> Thanks,<br>
> Sam<br>
><br>
> Sam Cohen, Principal<br>
> New Media Solutions<br>
> Drupal Training & Services<br>
> New Courses Starting Soon<br>
><br>
><br>
><br>
</div></div><div class="im HOEnZb">> _______________________________________________<br>
> consulting mailing list<br>
> <a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
> <a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
><br>
<br>
<br>
<br>
</div><span class="HOEnZb"><font color="#888888">--<br>
Steve Purkiss<br>
<br>
<a href="http://purkiss.com" target="_blank">http://purkiss.com</a><br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
</div></div></blockquote></div><br>