<?xml version="1.0"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>MachForm Community Forums Topic: Subdomain Database Placement</title>
<link>https://www.machform.com/forums/</link>
<description>MachForm Community Forums Topic: Subdomain Database Placement</description>
<language>en</language>
<pubDate>Sat, 06 Jun 2026 19:59:18 +0000</pubDate>

<item>
<title>yuniar on "Subdomain Database Placement"</title>
<link>https://www.machform.com/forums/topic/subdomain-database-placement#post-11669</link>
<pubDate>Thu, 24 Mar 2011 13:43:29 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">11669@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;Hi Ed,&#60;/p&#62;
&#60;p&#62;Yes, I suggest to create separate database for each subdomain. So that the data between those subdomains won't interfere each other.&#60;/p&#62;
&#60;p&#62;I'm not sure about what you mean by placing all d/b in the site root though?&#60;br /&#62;
Do you mean placing the machform files?&#60;/p&#62;
&#60;p&#62;If so, I suggest to put them into the document root of each subdomains.
&#60;/p&#62;</description>
</item>
<item>
<title>edparrott on "Subdomain Database Placement"</title>
<link>https://www.machform.com/forums/topic/subdomain-database-placement#post-11665</link>
<pubDate>Wed, 23 Mar 2011 23:36:24 +0000</pubDate>
<dc:creator>edparrott</dc:creator>
<guid isPermaLink="false">11665@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;Howdy! I have purchased an unlimited license with the intent of using Machforms on many protected sub domains, and I assuming a different database is advisable for each. The question I have is this, is it best to place all d/b's in the site root, or should I look at placing them in the root of each sub?&#60;/p&#62;
&#60;p&#62;Many Thanks for an excellent and reasonably priced product!&#60;/p&#62;
&#60;p&#62;  -Ed Parrott
&#60;/p&#62;</description>
</item>

</channel>
</rss>
