Monday, March 12, 2012

multiple database performance

I'm planning on creating multiple databases on a client because I'm storing a large amount of binary data (jpg's and pdf's) in tables and there are size limitations for a single database. So, in order to get around the size limitations, I'm just creating one database for my main tables and multiple other databases to hold the binary data.

Any performance considerations I should consider in regards to multiple databases? Any other thoughts?

Hi,

what about not storing the data in the database ? Do a quick one on this document, it has some detailed information for your design:

http://research.microsoft.com/research/pubs/view.aspx?msr_tr_id=MSR-TR-2006-45

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||First, what size limit in SQL 2005 are you trying to avoid?

Second, as someone else pointed out, saving files in the database is not a good design. The main problem is, what do you do with them once they are there? How do you get them out? The OS is much better at saving files efficiently than SQL. Creating an "index" database into the files is a much better method.

To answer your question, it depends on your design and situation. What are you going to do with the data, how do you query the databases, etc. There is very little impact in selecting data from tables in different database on the same sever.|||I think I may have posted this in the wrong group (I am actually going to use SQL Server CE), but the 2 responses were extremely helpful. Thanks!

No comments:

Post a Comment