Database server layout

Hi All,
Being small, we have only one database server that serves our need (SQL
2000 Enterprise Edition). We never had any replication or mirroring.
Now we will be installing SQL 2005.
I was asked to look into the best way of creating a good database
server so that we will not have any downtime.
At the present if we need to stop/restart or something goes wrong with
the server, then we loose many working hours sometimes even a few days.
Could you please point me the right direction (articles, web link) so
that I can see an example of good database server layout?
I do appreciate your help.
Thanks a million in advance.
Best regards,
MamunHi Mamun
I would suggest the best and most cost effective solution with the lease
amount of administrative effort would have to be mirroring. THe SQL Native
Client monitors the server status and fails over automatically for you and
your applications can continue working without have to re-establish
connection again of having to wait for failovers to complete. We tested
mirroring extensively and achieved failover in 5 sec, MS claim u can be up
and running on the mirror instance in 3 sec.
have a look at it, i'm sure it would fulfill all your needs
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
--
http://www.sqlserver.co.za
"mamun_ah@.hotmail.com" wrote:
> Hi All,
> Being small, we have only one database server that serves our need (SQL
> 2000 Enterprise Edition). We never had any replication or mirroring.
> Now we will be installing SQL 2005.
> I was asked to look into the best way of creating a good database
> server so that we will not have any downtime.
> At the present if we need to stop/restart or something goes wrong with
> the server, then we loose many working hours sometimes even a few days.
>
> Could you please point me the right direction (articles, web link) so
> that I can see an example of good database server layout?
> I do appreciate your help.
> Thanks a million in advance.
> Best regards,
> Mamun
>