swartout
asked on
Use 1 or more Databases
I am in the process of creating a large website. Should I have a different database for each of my systems? For example, I have 400 clients now, would like this number to increase, and each of them will have access to atleast one of my systems. And within that system for that client they might have up to 10 users(maybe even more). I currently have 5 different systems that I am working on incorporating into my website. I currently have 1 database with my account and user and system information. I now want to start working on one of these systems. I have many different functions that my user will be able to perform and therefore this will get quite large. Should I create a new database for all of this information? I am currently using Microsoft Access, should I switch to SQL Server?
ASKER
The systems do have links to each other, but are truely seperate applications.
I have one database set up now, that contains my login information, which consists of accountnumbers, usernames and passwords. Also in this database I have the information regarding what systems these users have access to. If they have access to the system, then I was going to call up the new database to take over from there, which would need to have accountnumber in it to let the user only have access to their account information.
The main link between my two main systems is descriptions of levels and their values. If they have purchased both of these, then we would want those identifiers to be consistant in both applications.
I do not know anything about SQL Server, what would I need to do to get started using it? Is it SQL Server or MysQL? I have heard of both of these.
Thanks.
I have one database set up now, that contains my login information, which consists of accountnumbers, usernames and passwords. Also in this database I have the information regarding what systems these users have access to. If they have access to the system, then I was going to call up the new database to take over from there, which would need to have accountnumber in it to let the user only have access to their account information.
The main link between my two main systems is descriptions of levels and their values. If they have purchased both of these, then we would want those identifiers to be consistant in both applications.
I do not know anything about SQL Server, what would I need to do to get started using it? Is it SQL Server or MysQL? I have heard of both of these.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks again for all of your assistance.
As far as having multiple databases... this is really up to you. If your systems have any link to each other, then you might consider using the same DB for each, but if they are really seperate applications...I'd suggest leaving them seperate. There's no reason to mix this data if there is no relation.
Something you might consider is to have a seperate DB setup just for user accounts. This way, the user accounts are centralized rather then a user table in each DB. You may also consider putting some security tables in this 'user' database that will control each users access to each system you have setup.
To get a real answer, we'd need to know more about your systems and their relationships to the users and each other.