SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


In a snapshot replication, users will be able to connect to the replica while replication is...


In a snapshot replication, users will be able to connect to the replica while replication is running?

Author
Message
paula_ancaI
paula_ancaI
Grasshopper
Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)

Group: General Forum Members
Points: 24 Visits: 28
Situation:
Server A replicated on server B, snapshot replication on every 30 min, DB size 4Gb.
Are users able to connect to server B while Snapshot/Distribution Agent running? Server B is set for reporting purpose and users are running the reports all time, even in the snapshot replication laps of time.
Pradyothana Shastry
Pradyothana Shastry
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2215 Visits: 507
Users can fetch reports from server B


- Pradyothana


http://www.msqlserver.com
paula_ancaI
paula_ancaI
Grasshopper
Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)

Group: General Forum Members
Points: 24 Visits: 28
Thank you Smile !
sorry for my laconic ton, I am overloaded and it shows.
Chand00
Chand00
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1582 Visits: 1257
Why dont you consider Transactional replication. I think it suits your environment. Initially the snapshot is generated and gets reflected at the subscriber and transactions that happen at the publisher will get reflected automatically at the subscriber without any problem.

Thanks
Chandra Mohan N

Thanks
Chandra Mohan

paula_ancaI
paula_ancaI
Grasshopper
Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)

Group: General Forum Members
Points: 24 Visits: 28
Is that I proposed first time - transactional replication - but the client don't want to add the primary key for all tables. Result: no transactional replication! and they want all that replicated, no just some tables for the purpose of reporting.
Thanks,
Paula
edmund chan
edmund chan
Mr or Mrs. 500
Mr or Mrs. 500 (555 reputation)Mr or Mrs. 500 (555 reputation)Mr or Mrs. 500 (555 reputation)Mr or Mrs. 500 (555 reputation)Mr or Mrs. 500 (555 reputation)Mr or Mrs. 500 (555 reputation)Mr or Mrs. 500 (555 reputation)Mr or Mrs. 500 (555 reputation)

Group: General Forum Members
Points: 555 Visits: 132
Snapshot Replication might no be a good solution. Since it drops all objects and re-create them, I am sure the users will get disconnected somehow. Not only that, you may encounter some locking/blocking issues on the source server while the snapshot is generating.

Ed
2 Tim 3:16
2 Tim 3:16
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: General Forum Members
Points: 1811 Visits: 1547
I think a log shipping solution may be a little faster. Yes, the users will be knocked off when you restore the tran log (same as snapshot replication) but you're only restoring the tran log and not the entire DB.

Tim White
steve block
steve block
SSCommitted
SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)

Group: General Forum Members
Points: 1876 Visits: 1563
There are some options besides dropping a table and recreating it for snap shot replication (at least there is for SS 2000). You can "Delete all data in the existing table" instead of dropping the tables. This could reduce the time that tables are not available but if there is a table structure change, this could cause problems.

I would recommend once a day, off hours snapshot replication or bite the bullet, add the primary key to all tables needed and use transaction replication. I'm sure that there are some articles on SSC that would give some useful arguements for setting up a relational database with primary keys.

Steve



Kendal Van Dyke
Kendal Van Dyke
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1564 Visits: 983
Users can connect to Server B but will not be able to select from whatever table the snapshot agent is currently working on since it will be locked by the bcp process the snapshot agent is running.

but the client don't want to add the primary key for all tables

Wow Blink...What a great opportunity for you to teach your client about why it's a good idea to put a PK on tables.

While other people have mentioned log shipping and it sounds like it may be applicable to your situation, remember that log shipping covers the entire database. If you're replicating every table perhaps log shipping is a better solution. If you're replicating only a few tables log shipping may not be the best solution.

Kendal Van Dyke
http://kendalvandyke.blogspot.com/
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search