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

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SS2K5 Replication » In a snapshot replication, users will be able...

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

Rate Topic

Display Mode

Topic Options

Author

Message

paula_ancaI

Posted Thursday, June 18, 2009 10:42 AM

Forum Newbie

Group: General Forum Members
Last Login: Monday, January 17, 2011 7:31 PM
Points: 5, Visits: 22

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.

Post #737765

Pradyothana Shastry

Posted Thursday, June 18, 2009 11:07 AM

SSCommitted

Group: General Forum Members
Last Login: Monday, March 25, 2013 5:30 AM
Points: 1,641, Visits: 423

Users can fetch reports from server B

- Pradyothana

http://www.msqlserver.com

Post #737781

paula_ancaI

Posted Thursday, June 18, 2009 11:40 AM

Forum Newbie

Group: General Forum Members
Last Login: Monday, January 17, 2011 7:31 PM
Points: 5, Visits: 22

Thank you :) !
sorry for my laconic ton, I am overloaded and it shows.

Post #737797

Chand00

Posted Friday, June 19, 2009 9:56 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Saturday, March 02, 2013 4:42 AM
Points: 525, Visits: 1,096

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

Post #738469

paula_ancaI

Posted Tuesday, June 23, 2009 7:53 AM

Forum Newbie

Group: General Forum Members
Last Login: Monday, January 17, 2011 7:31 PM
Points: 5, Visits: 22

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

Post #740176

edmund chan

Posted Tuesday, June 23, 2009 3:14 PM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Tuesday, October 26, 2010 1:39 PM
Points: 545, 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

Post #740589

2 Tim 3:16

Posted Wednesday, June 24, 2009 7:18 AM

Ten Centuries

Group: General Forum Members
Last Login: Today @ 1:50 PM
Points: 1,081, Visits: 1,454

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

Post #741011

steve block

Posted Wednesday, June 24, 2009 7:57 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, May 21, 2012 3:13 PM
Points: 516, Visits: 1,563

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

Post #741044

Kendal Van Dyke

Posted Thursday, June 25, 2009 9:16 AM

Old Hand

Group: General Forum Members
Last Login: 2 days ago @ 10:23 AM
Points: 361, Visits: 781

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

...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/

Post #741896

« Prev Topic | Next Topic »

Permissions