| Author |
Topic |
|
ymphyu
Starting Member
4 Posts |
 Posted - 2011-01-11 : 12:16:16
|
| Hi,I am new to database replication and SQL job scheduling.I want to setup a scheduled job in SQL Server 2005, I know when it will start but I don't know how long it will take to complete the job.But my worry is when the replication started what will happen to the job that is currently running?Any idea?Thanks,ymphyu |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
ymphyu
Starting Member
4 Posts |
Posted - 2011-01-11 : 12:24:11
|
| The job will run the exe. That exe file will generate series of report files using the database (subscriber data) that is going to replicate data from another server (publisher server).Sorry if I use the wrong term.My worry is while exe file is process and replication process is started, what is going to happen to my exe process.doesn't it make sense? |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
ymphyu
Starting Member
4 Posts |
Posted - 2011-01-11 : 12:32:22
|
| command line exe application will be written by .NET C# |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
ymphyu
Starting Member
4 Posts |
Posted - 2011-01-11 : 12:37:18
|
| Thanks for trying to help anyway |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-01-11 : 14:24:15
|
| Sounds like your exe will be generating reports by reading (SELECTing) from the subscriber?In this case, you'll just want to make sure that reads don't block the writes. I have seen the distribution agent fail as a deadlock victim.Two things I would do: (1) make sure the distribution agent will retry and not just crash on error, else you'll be manually snapshotting and resynching on every error. You set this in the agent profile. (2) Set the isolation level of the subscriber database(s) to READ_COMMITTED_SNAPSHOT. This will prevent the reads from blocking the writes, but does add some overhead. |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-01-11 : 14:26:34
|
By the way, if you do set the agent to continue (essentially ignore) on errors, you'll want to create a job or an alert so you know about it. Else you run the risk of the subscriber getting out of synch with the publisher over time.And don't we all hate it when asked "why doesn't this report match this..."  |
|
|
|
|
Database Replication and SQL Job