Thanks for your reply, i think point1 can be the issue.

can you guide me how to check it if it has proper permission?

(1) The account under which SQL Server Agent...

I got the answer, IT team has intalled IPS on each location which is blocking SP_CMDSHELL to execute at other location to avoid SQL Injection.

Just to add on above issue, i am not able to run the below as well

"EXEC master..xp_cmdshell 'DIR'" from my machine.

any suggestions??

Just to add on above issue, i am not able to run the below as well

"EXEC master..xp_cmdshell 'DIR'" from my machine.

any suggestions??

no, SP3

i am getting the same issue, does anybody has any solution for this.

ok, here's the details:

No of Publisher : 3

No of Publication each Publisher: 35

No of Article per Publication: few has 4/5 (very big tables) others 10 / 15

No of Subscription per...

300 Distribution agent: Correct, thats the load i want to reduce, for Pull we have to change the complete replication scenario of our company(we can still check that later) ...

my mistake,

read it as publisher server not publication

Just to explain a bit more.

We have three server from which we are publishing data to 10 subscriber.

too many transaction are going on...

Another option is to use SSIS/DTS to transfer data.

thanks for the concern Lutz, i will rethink all again how to go ahead on this or to drop the idea.

thanks all for your kind suggestions , i will rethink what we can do.

thats because we (DBADMINS) coverage in not 24*7 and we are receiving request for these one liner update in off hours and needs to be done ASAP, it cannot wait...

thats the problem, we cannot run it in test enviorment as the code we are planning to give them are just one liner like

"update tablename set columnname=1 where columnname=2"

this...

yes thats correct, we are planning to give access to some database programmer to update production data but still want to be safe (if they forget to put where or...