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 |
|
Blastrix
Posting Yak Master
208 Posts |
 Posted - 2002-12-14 : 18:25:52
|
| Up until this point we have been okay having our database setup on the same server as the webserver. So if the server crashed, it didn't matter because everything was down anyways. The time has come to remove the DB and webservers from each other. The tentative plan is to have two web servers which talk to the database server. Well what happens when the database server crashes, or routine maintenance needs to be done? How do you setup two databases that contain the exact same information, that can either be hit at the same time, or having one serve as a backup for the other? Any insight on this would be most appreciated.Thanks,Steve |
|
|
rkc01
Starting Member
43 Posts |
Posted - 2002-12-14 : 19:43:40
|
| You could replicate or log ship. Check out BOL for an explanation of each. Log shipping works well in our environments. Depends on your exact needs. Microsofts site also has a couple good white papers.rob |
 |
|
|
rkc01
Starting Member
43 Posts |
Posted - 2002-12-14 : 19:56:15
|
| I forgot to mentions a pretty cool 3rd party app that I've tested. It's called SQLUP. It's software that clusters the servers, (for automatic failover) and replicates the database between. I liked it because there is no shared array and the boxes don't need any special hardware. Only requirements are 1/2 GB Ram, WIN2K Server and SQL2K. The guys who wrote the app were also very good to work with. |
|
|
|
harshal_in
Aged Yak Warrior
633 Posts |
Posted - 2002-12-15 : 02:43:55
|
quote:
I forgot to mentions a pretty cool 3rd party app that I've tested. It's called SQLUP. It's software that clusters the servers, (for automatic failover) and replicates the database between. I liked it because there is no shared array and the boxes don't need any special hardware. Only requirements are 1/2 GB Ram, WIN2K Server and SQL2K. The guys who wrote the app were also very good to work with.
replication is the solution i guess.I had the same stuation at my company in the last week and we seperated the web server and the database server after the web server crashed.I have set up a backup server for emergency,using replication.harshal |
|
|
|
|
|
|
Multiple Databases / Backup Server?