Snapshot Replication for the Beginner
-
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/awarren/snapshotreplicationforthebeginner.asp>http://www.sqlservercentral.com/columnists/awarren/snapshotreplicationforthebeginner.asp
-
We have been playing around with snapshot replication, but our tables are NOT owned by dbo.
When we replicate the default option sets the destination tables to be DBO (even though the Source table owner shows correvtly), the only way we can change this is to set the correct destination table owner for each table (a time consuming business).
-
Thank you for taking the time to post this article! You've done an excellent job in bringing those who are not quite the replication guru along. I do hope that you continue on this series until you have covered everything - this will serve me well. Thanks again..
-
Thanks for the Article. I think it was very informative and well written. Please do address the issue of handling identity columns. This is something I have not found many articles address. I would really appreciate if at some point you can address on how to include identity columns for snapshot replication without having to create the data structure at the subscriber.
Thanks and Rgds,
Sam
-
The article is quite good at showing some the relatively simple (yet powerful imho) reasons why replication is a good idea...I am in the process of finishing a document for merge replication. I hope on your continuation of the articles you also talk about security concerns with replication (eg getting the right permissions on the folder which holds the published db for others to subscribe to) I am currently wrestling with how to make it secure enough..of course this is for merge and not snapshot...once again great article !
My next step after figuring out merge rep for SQL is to take it to the SQLCE format...if i beat you to the punch i may be able to write a column on what you have to do for SQL CE replication (merge)
------------------------------
Life is far too important to be taken seriously -
Good. can you give some tips for replication between MsAccss 2000 and SQL Server 2000 database.
-
-
I've selected option "Immediate updating" on step Updatable Subcriptions, but when I inserted a new row into subscriber, it not inserted into publisher, and this new row disappeared after a time I set up in schedule. What's wrong? Can anyone help me?
-
Hi Folks,
I have recently set up Snapshot replication in my team . The DB is usually about 9GB in size. But from during the same time replication started, I see 12 new tables added to the DB (at Publisher):
dbo.MSpeerIsns,
dbo.MSpeer_request,
dbo.MSpeer_response,
dbo.MSpeer_Identity_range,
dbo.sysarticlecolumns,
dbo.sysarticles,
dbo.syspublications,
dbo.sysreplservers,
dbo.sysschemaarticles,
dbo.syssubscriptions,
dbo.systranschemas
My questions are:
1. with Snapshot Replication going on with 2 subscribers hosted on a different server, will the transaction log on the publisher increase?( does snapshot replication have anything to do with transaction log's increase in size? )
[ note: The subscribers are initializing(syncing) constantly and the publisher does a snapshot dump to a share twice daily) note that over the past week, the publisher DB size has increased to 22GB. It could be the actual data thats being pushed into the DB, or it could be Replication. I'm trying to remove Replication as a culprit to transaction log size increase.]
Thanks in advance,
Kiran
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply