There's no such thing as a stupid question, but they're the easiest to answer.
JoinTour
Login
 
Tag Cloud
access audio avg avg 8 bios blue screen boot bsod computer connection cpu crash css dell desktop dma driver drivers dvd email error excel explorer firefox firefox 3 freeze gimp graphics hard drive hardware hijackthis hjt install internet internet explorer itunes keyboard laptop macro malware monitor motherboard network networking outlook outlook 2003 outlook 2007 outlook express pio problem problems router seo server slow sound sp3 spyware trojan usb video virtumonde virus vista vundo windows windows vista windows xp winxp wireless
Web Design & Development
Search
Search in:
 
Advanced Search
Tech Support Guy Forums > Internet & Networking > Web Design & Development >
Good database keeping (MySQL)


HELLO AND WELCOME! Before you can post your question, you'll have to register -- it's completely free! Click here to join today! We highly recommend that you print a copy of our Guide for New Members. Enjoy!

 
Thread Tools
dmurfitt's Avatar
Senior Member with 618 posts.
 
Join Date: Nov 2002
02-Feb-2006, 07:14 AM #1
Good database keeping (MySQL)
Our host plan has given us 1 MySQL database. I want to be able to use this database for our website to store test results, comments etc. We also develop some websites for our customers, is it a bad idea to store their data in our database too, even if it's not related to our data in any way at all? This would save upgrading to the next plan up or buying extra databases, but I don't want to have a mess of data at the same time. Thanks.
GCDude's Avatar
Senior Member with 400 posts.
 
Join Date: Apr 2005
Location: Brighton, UK
Experience: Possibly Competent
02-Feb-2006, 08:40 AM #2
Well you have to weigh up the cost of extra mysql databases, the organisation of diff websites tables and if you are having lots of traffic, the performance of the 1 db.

To start with i would run off the 1 db and organise your naming of tables such as-

OurWebsite_table1, OurWebsite_Table2............
customer1_table1, customer1_table2...........
customer2_table1, customer2_table2............

then if things start getting slow, youll then have the choice of buying more db's and moving customer tables, depending on load.
dmurfitt's Avatar
Senior Member with 618 posts.
 
Join Date: Nov 2002
02-Feb-2006, 08:43 AM #3
That's what I've started to do, I just wasn't sure if it would be a good idea or not, don't want the whole thing to fall over. Thanks for the advice mate
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are Off
Refbacks are Off

You Are Using:
Server ID
Advertisements do not imply our endorsement of that product or service.
All times are GMT -4. The time now is 10:15 PM.
Copyright © 1996 - 2008 TechGuy, Inc. All rights reserved.
Powered by vBulletin, Copyright © 2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.1.0
Powered by Cermak Technologies, Inc.