------ =_NextPart_001_01BF7450.B082C200
Content-Type: text/plain
Has Iea-Software published any documentation / white paper on a good
solution for redundancy? We are talking about NT here!!
I have two SQL 7.0 boxes that I want to accomplish this with. With
efficiency / performance being a factor, I am curious how I can do the
following:
Primary Auth and Accounting, if it goes down, let backup pickup where it
left off and then when the primary is backup, update the primary, my
only concern is that my calls table is very active and I may lose
transactions.
Doing transaction publishing every second may not be the best way to
accomplish this.
Any suggestions??
Thanks,
Sean Herr
------ =_NextPart_001_01BF7450.B082C200
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
Has Iea-Software published any =documentation / white paper on a good solution for redundancy? We are =talking about NT here!!
I have two SQL 7.0 boxes that I want =to accomplish this with. With efficiency / performance being a =factor, I am curious how I can do the following:
Primary Auth and Accounting, if it =goes down, let backup pickup where it left off and then when the =primary is backup, update the primary, my only concern is that my calls =table is very active and I may lose transactions.
Doing transaction publishing every =second may not be the best way to accomplish this.
Any suggestions??
Thanks,
Sean Herr
------ =_NextPart_001_01BF7450.B082C200--