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 |
|
ghank
Starting Member
2 Posts |
 Posted - 2002-03-28 : 18:28:22
|
| Here is the situation:Our company makes vertical market software for the legal market. In order to use the software a user has to register and receive a password or unlock code.We have until now done this over the phone with customers. Now we aredeveloping a Web based system where customers can register and receive a password on our website however some customer will be unwilling or unable to register over the Web. In this case we still have to do the registration via a web based interface or use Access as a front end (there are a number of options). This is all fine except our DSL goes out for a few hours typically once or twice a month. Our site is hosted by an ISP in Texas. We are Minnesota. We have DSL and SQL server 2000. They have redundant T1 lines and redundant power. This seems like a job for replication. I just don't know which server should be the publisher and whether the subscriber should have read only copy or use one of the models (merge for example) where the publisher and subscriber. Suggestions please. |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2002-03-28 : 19:22:01
|
| I know it's not what you want to hear, but I would suggest finding a new DSL service provider.------------------------GENERAL-ly speaking... |
 |
|
|
ghank
Starting Member
2 Posts |
Posted - 2002-03-29 : 11:23:38
|
| [quote]I know it's not what you want to hear, but I would suggest finding a new DSL service provider.------------------------My understanding is this is the nature of DSL. It generally works very well but does go down 1-2x per month for a few hours. Our DSL provider resells COVAD DSL and the only other option in our area is QWest (commonly known as Qworst in our office). Even if there was another good DSL option I wouldn't be inclined to switch because as stated above DSL is pretty good but not as reliable as T1 |
|
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2002-03-29 : 14:06:51
|
| Replicating from where to where? Are you saying you have SQL Server installations in both Texas and Minnesota?setBasedIsTheTruepath<O> |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2002-03-29 : 15:21:26
|
quote:
Replicating from where to where? Are you saying you have SQL Server installations in both Texas and Minnesota?setBasedIsTheTruepath<O>
Thats a good question... When I read it, I see that there is an Access DB (maybe with linked tables to SQL2k) and a SQL2k box at his location... So then whats at the WEB?Not knowing your setup and going with the idea that you want to use replication AND assuming that SQL Server is at both sites: I would setup Merge replication between the 2 servers. This would allow for both SQL Servers to take registrations and then when your DSL came back up they would send each other the data that each recieved while it was down. I'm not sure but I think your replication distribution job would fail and you would need to manually restart it if the DSL didnt come backup before the job ran out of retries.But if SQL Server was at both sites with the same data then why isnt replication being used anyway?DanielSQL Server DBA |
|
|
|
|
|
|
Suggestions on replication