Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jay1648
Starting Member
1 Post |
 Posted - 2008-06-17 : 04:34:50
|
| Hi, I'm planning to develop a project on .NET using Sql server 2005. Just stuck at a point where I need to decide that Should I use 2 or 3 huge databases with a lot of tables and data into it or should i create a lot of databases which would contain small chunks of data. Please let me know which option would give me a better performance. Thanks in advanceGod is great. We are not God. But we still can be great. |
|
|
suresha_b
Yak Posting Veteran
82 Posts |
Posted - 2008-06-17 : 07:33:19
|
| Huge/big database means how big in size?2 or 3 huge databases are easy to maintain. It will be convenient for developers also. Performance also should be better as there are fewer disk files and IO. |
 |
|
|
tosscrosby
Aged Yak Warrior
676 Posts |
Posted - 2008-06-17 : 12:03:48
|
| It all depends. What will the databases contain? Is the data within each potential database related? If so, one database should be fine. How large? Can you partition the data into separate files, on separate physical disks? That would help with respect to performance. Indexing is key. What type of load are you expecting? A lot of question marks that need to be answered before you can get any responses that will truly help. Again, size of the database would be a key factor. I have seen terabyte databases that performed very well because of the disk setup, proper indexes, routine maintenance performed, etc.Terry |
|
|
|
|
|
|
Multiple Small databases vs Single Big Databas