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 |
|
rikleo2001
Posting Yak Master
185 Posts |
 Posted - 2007-11-08 : 15:44:55
|
| Hi,I setup transactional replication between 2005-> 2000 database for only one table. It works fine no problem. I checked replication monitor everything works well.My Subscription was Push Subscription on Publisher.This morning I restored main database at publication server, I saw all my publication configuration were gone.I then went to create a publication and push subscription again..and did it, But when I went to replication monitor.I checked that Snapshot are being created, but from distributor to Subscriber is saying below message?"The concurrent snapshot for publication is not available because it has not been fully generated.....lONG CHPPPED off meassage"Can any body tell me hwo to get over this issue?Many ThanksSKR |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-11-08 : 16:22:48
|
| Tried start snapshot agent? |
 |
|
|
rikleo2001
Posting Yak Master
185 Posts |
Posted - 2007-11-08 : 16:39:27
|
| did that and it is working, creating snapshot everyminute. thanksSKR |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-11-08 : 16:47:40
|
| Running a snapshot every minute is not what you want to do for transactional replication. Snapshots are rarely performed. Why did you set it to run every minute?Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
rikleo2001
Posting Yak Master
185 Posts |
Posted - 2007-11-08 : 17:27:35
|
| Tara, Thanks.My Trasactional replication is setup on only one table at this stage.It is timesheet entry database table, which is upgraded to SQL Server 2005, currently this is being used by only 2 peoples (Pilot application).I want to replicate any entry whatever they made into sql server 2005 database back to SQL Server 2000 databases.That's why I did it this way.I know snapshot is not idea for heaving data transfer, but this is only for 1 MB snapshot transfer till we go live.I resolve this issue by disabling publishing and distributor (running it through TSQL)Many Thanks......CheersSKR |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-11-08 : 17:33:29
|
| You don't need a snapshot to run in order for the updates to happen at the subscriber. You only needed the snapshot this time around to get the initial data and object over at the subscriber. You no longer need the snapshot!Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
rikleo2001
Posting Yak Master
185 Posts |
Posted - 2007-11-08 : 17:45:56
|
| Tara, thanks again.Sorry I am not that expert in replication area. Just want to clarify.So you are saying in Transactional replication when it asks for a schedule of Snapshot, I can only say run only one time.Once it executed, then I don't need it for transactional process.Logreader agent will take over and will gather every transaction from the log and will push it distributor? rest distributor will push it to subscriber?Many Thanks..SKR |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-11-08 : 17:47:19
|
| That's correct.Your snapshot job probably wasn't doing anything every minute anyway as I'm sure it was noticing that it didn't need to do any work. You should of course test that you still get the data at the subscriber after you have modified the snapshot job.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
|
|
Transactional Replication from 2005 to 2000 Issue