Design DBs with HA in mind

Is there any article,white paper etc that tells me how to design my
databases with High Availability in mind..
Im not talking about clustering,log shipping,etc. that can help prevent
hardware failures but to minimize downtime by designing the databases such
that customers are broken down by names or geographic locations, etc.. that
would help prevent losing the entire customer db should the server be
unavailable and hence total outage to the application.
I am looking for ways on how clients have designed their apps..
I hope this makes sense... I am not looking for too much details but just
some generic overview would immensely help
ThanksHi
You may want to look at table partitioning and the ability to restore
filegroups offered in SQL 2005.
http://msdn2.microsoft.com/en-us/library/ms190787(SQL.90).aspx
Or you can look at a federated database and partitioned views (distibuted or
locally) in both SQL 2000 and SQL 2005
http://msdn2.microsoft.com/en-us/library/ms191185(SQL.90).aspx
HTH
John
"Hassan" wrote:
> Is there any article,white paper etc that tells me how to design my
> databases with High Availability in mind..
> Im not talking about clustering,log shipping,etc. that can help prevent
> hardware failures but to minimize downtime by designing the databases such
> that customers are broken down by names or geographic locations, etc.. that
> would help prevent losing the entire customer db should the server be
> unavailable and hence total outage to the application.
> I am looking for ways on how clients have designed their apps..
> I hope this makes sense... I am not looking for too much details but just
> some generic overview would immensely help
> Thanks
>
>