| Author |
Topic |
|
Ken Blum
Constraint Violating Yak Guru
383 Posts |
 Posted - 2003-12-11 : 16:47:40
|
| I've been searching for a way from the the excellent people here(Tara, Vyas to mention a few) for help on how to synchronize data between SQL Servers on subscribers that will not be connected to the network such as laptops.Pull subscriptions are created at the Subscriber, and the Subscriber requests data and updates made at the Publisher. Pull subscriptions allow the user at the Subscriber to determine when the data changes are synchronized, which can be on demand or scheduledIs there any reason I should not use a Pull Subscription, and if so can the synchronization be called via T-SQL and/or the activex controls? Thanks once again for all of your help. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-12-11 : 16:56:23
|
| How big of a database are we talking about? Does the laptop need to be updated each time that it comes on the network?Everything can be called via T-SQL if it is SQL Server work that you are doing.Tara |
 |
|
|
Ken Blum
Constraint Violating Yak Guru
383 Posts |
Posted - 2003-12-11 : 17:13:53
|
| Fairly small. Transactional Replication will include a database of Customers/Emmployees, 6 columns and right now at 3,000 rows, and a sales order database, 2 columns, 14,000 rows. These are just "Cross Reference Tables" which will not be updated that frequently by the publisher.Intend on also having various Merge Replication of data like Expense Reports, but the data the subscriber will get will be relevant to him or his subordinates, so it will be fairly limited. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-12-11 : 17:16:27
|
| If it weren't for the subscriber needing to update the publisher, then I would say go with the BACKUP/RESTORE approach as long as the publishing database was small enough for quick backups and restores.Tara |
|
|
|
Ken Blum
Constraint Violating Yak Guru
383 Posts |
Posted - 2003-12-11 : 17:19:02
|
| Do you have something against Pull subscriptions? I would think that this would be the best method since only the data that has been changed is being transferred. Isn't that the idea behind Replication? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-12-11 : 17:26:05
|
| No, I have nothing against pull subscriptions.Yes that is the idea behind replication. But I would think it would be an overkill for a small database. How small in MB is the publishing database?Tara |
|
|
|
Ken Blum
Constraint Violating Yak Guru
383 Posts |
Posted - 2003-12-12 : 11:59:14
|
| The database I am using as a transactional publication "cross reference" is 5GB. I will also have a database for the merge replication, which I have only partially designed but it will be fairly small (Expense reports, Service reports, etc.).Right now I am only publishing 4 tables out of 2,200 from the transactional replication publishing database, so that result is quite small. I am also filtering the columns on the these tables to the subscriber so they only get what they need. For the tables in the merge replication, I will be filtering rows based on what the subscriber gets to see/modify/insert. It seems to me that this filtering capability is another reason I should be using replication. Would you agree?There will be 100+ subscribers using this replication (not concurrently) via MSDE. Do you know of any limitations regarding replication via MSDE? I've always been told that the only limitation is the number of concurrent connections.Since these subscribers will be connected for only a brief time on a periodic basis to synchronize/transfer this data, it would seem to me that Pull Subscriptions are ideal. I plan on writing one user-fiendly program to execute the synchronization process on a user demand basis via T-SQL or ActiveX on that will reside on the susbscriber side. The beauty of this will be that we can then use any user-friendly 3rd party program (like a forms tool or custom app that I write) to modify the SQL data on the subscriber side, without the requirement that the 3rd party tool handle the replication synchronization.How do you like my plan so far? I really appreciate your advice. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-12-12 : 12:17:00
|
| I don't know of any limitations with MSDE in regards to replication.It sounds like you are heading down the correct path. Tara |
|
|
|
Ken Blum
Constraint Violating Yak Guru
383 Posts |
Posted - 2003-12-12 : 12:27:57
|
| Thanks Tara. That's good to hear. I will let you guys know how it all works out. I'm sure I'll be back with something else!I'm an expert on some other forums and know how advising on these forums can be a time-consuming and sometimes frustrating process. So I REALLY APPRECIATE your help and time.I'll be back... |
|
|
|
|
Pull Subscriptions for Replication on Laptops?