Answers and the truth.. Need advice on replication..

First off I have...
A) I have a database with no primary keys ..
B) I have two machines setup with SQL 2000 Advanced..
C) One with my data on it running in production right now...
D) An app which uses ODBC to connect..
What are my options and my best route for redundancy and high availability
of this database//?
Thanks,
Jeff
That depends.
For automatic failover you need clustering. Clustering is very expensive.
Clustering's latency can be 1-2 minutes. Clustering requires SQL 2000
Enterprise, which I assume is what you mean by SQL 2000 Advanced.
With log shipping you get redundancy at a low cost but lower latency.
Latency typically is 5 minutes, but can be much less depending on the size
of the logs you are restoring. There is no automatic failover with log
shipping. SQL 2000 Enterprise edition has a log shipping wizard, but you can
roll your own solution. Here is an example:
http://www.sql-server-performance.co...g_shipping.asp
You can also use replication. By default transactional replication needs
primary keys on the tables you are replication, but there are ways around
this. Please see this link:
http://groups.google.com/groups?selm...&output=gplain
Other than that you can use merge.
Latency is typically around 1 minute.
With replication there is no automatic failover.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Jeff Bade" <jbade@.collidingstar.com> wrote in message
news:8Gdbd.7702$5b1.5654@.newssvr17.news.prodigy.co m...
> First off I have...
> A) I have a database with no primary keys ..
> B) I have two machines setup with SQL 2000 Advanced..
> C) One with my data on it running in production right now...
> D) An app which uses ODBC to connect..
> What are my options and my best route for redundancy and high availability
> of this database//?
> Thanks,
> Jeff
>
|||Thanks for all the information.. This is a big help..
As far as Clustering.. Any problems I need to look at here?
Especially with no Primary Keys..
Or Login/Security rights?
Thanks,
Jeff
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23zIfPbesEHA.2668@.TK2MSFTNGP12.phx.gbl...
> That depends.
> For automatic failover you need clustering. Clustering is very expensive.
> Clustering's latency can be 1-2 minutes. Clustering requires SQL 2000
> Enterprise, which I assume is what you mean by SQL 2000 Advanced.
> With log shipping you get redundancy at a low cost but lower latency.
> Latency typically is 5 minutes, but can be much less depending on the size
> of the logs you are restoring. There is no automatic failover with log
> shipping. SQL 2000 Enterprise edition has a log shipping wizard, but you
can
> roll your own solution. Here is an example:
> http://www.sql-server-performance.co...g_shipping.asp
> You can also use replication. By default transactional replication needs
> primary keys on the tables you are replication, but there are ways around
> this. Please see this link:
>
http://groups.google.com/groups?selm...&output=gplain
> Other than that you can use merge.
> Latency is typically around 1 minute.
> With replication there is no automatic failover.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>