tag:blogger.com,1999:blog-3391250648133091392.post7446129003029253286..comments2008-02-05T23:21:29.413-05:00Curtis Keislernoreply@blogger.comBlogger1125tag:blogger.com,1999:blog-3391250648133091392.post-7575465877690817462008-02-05T23:21:00.000-05:002008-02-05T23:21:00.000-05:00I know this comment is just touching on a very small part of this post but i cant help but mention it.<BR/><BR/>If you divide your database architecture into a database-per-client model be aware of the deployment considerations for any and all SQL changes.<BR/><BR/>Keeping the schema and objects identical once such an implementation grows to a large scale will be a big challenge. I know of no deployment tools that specifically meet this scenario as at a company i worked for i was forced to build such tools myself (and with good results).<BR/><BR/>So yes it is possible to run an divide database infrastructure but just consider it from various angels. To me SQL Server always seemed better at one large database then many... many... many.. small ones.Dmitryhttp://www.blogger.com/profile/03066918323549754139noreply@blogger.com