![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
My company is looking at consolidating its Access databases from around the country into one centralised SQL resource. They are very worried about having all their 'eggs in 1 basket' and so are considering using clustering or a similiar solution. Unfortunately, whilst budgets can stretch for a small SAN and two decent servers - the huge cost of 2xSQL Server Enterprise edition is prohibitive. What are the options here? The application they use uses a DSN to connect to the database. Ideally, we would two servers each part of the same w2K cluster, therefore if one server broke down we couldn't have to change all the connection (DSN) information. Making sure that sprocs etc are identical between the two SQL servers isn't really an issue (as they don't really change) and we can always set a DTS package to transfer these peridocally. So, using SQL Standard edition and Windows 2000 Advanced server will this work? Two servers with the same logical name server name + same database name, replication from the master to the standby server. Will this cure my problem of having no fault tolerance and having to manually change the DSN's? Would really appreciate some help on this one!! Thanks very much Jof |
#3
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |