Thanks. It is a good point to split tables as Madscientist and Jeffrey pointed out, but I agree if the field are very specifice in name what can it hurt to add other feilds as IPSwitch does to the table. Also with only 300 user it would be great to have only one DB. I guess the finally question is can adding other fields in some way break Imail? I think I will try it this weekend and hope for the best come Monday! :)
Thanks everyone, ~Paul~ ----- Original Message ----- From: "Sanford Whiteman" <[EMAIL PROTECTED]> To: "Madscientist" <[EMAIL PROTECTED]> Sent: Tuesday, July 09, 2002 6:15 PM Subject: Re[2]: [IMail Forum] SQL Fields > Madscientist and Jeffrey wrote (approximately): > > > I think the safest design decision here is to create a second table > > for your redirection information and use a join in the query to > > retrieve it. > > I think this is overly cautious. A join uses more server resources and > will still require changes to the stored procedure syntax if IMail > column names or architecture should change. The chances of IMail > changing the basic DDL concept and somehow breaking for good your > extra columns are very small, and the workload of changing the name of > a column and updating your stored procedure is minimal. Deliberately > tag your column name with something site-specific (column names can be > quite long) and the chance of IMail requiring a column with the same > name is even slimmer. > > To take advantage of the simplicity of a single table, I'd say go > ahead. Many do when integrating with third-party apps. > > -Sandy --- [This E-mail scanned for viruses by Declude Virus/McAfee] Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Please visit the Knowledge Base for answers to frequently asked questions: http://www.ipswitch.com/support/IMail/
