.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
david stephan
Santhakumar Munuswamy
Asad Ali
Fauzul Azmi
Post New Web Links

How to name the agent job during setup replication

Posted By:      Posted Date: September 27, 2010    Points: 0   Category :Sql Server
 

hi, there

I am setup a new DB replication, during which I discover that there is no place to name the agent jobs for publisher, snapshot and subscriber, system wizard will name these jobs for me. But these name are ramdon and I wish they can be finalized before setup. Is there any way to do this work?

I have tried, 1) rename them after setup, but it seems risky since internally replication will interact with these jobs through name. 2) Setup place holder jobs before replication setup, and let new jobs overwrite these jobs, it does not work as wished and some of the job setting is not applied to new job.

Could any one help me out? And it will be great if your way can be done programmatically.

 




View Complete Post


More Related Resource Links

Error: The replication agent has not logged a progress message in 10 minutes

  
Hello,      We are consistently getting the error message below on our subscribers that have blob images. Is there a way to increase a setting to avoid SQL to throw this error, or another suggestion? Thanks in advance.   John   Error messages: The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.   18 -BcpBatchSize 10000018 -ChangesPerHistory 10018 -DestThreads 218 -DownloadGenerationsPerBatch 518 -DownloadReadChangesPerBatch 10018 -DownloadWriteChangesPerBatch 10018 -FastRowCount 118 -HistoryVerboseLevel 318 -KeepAliveMessageInterval 30018 -LoginTimeout 1518 -MaxBcpThreads 218 -MaxDownloadChanges 018 -MaxUploadChanges 018 -MetadataRetentionCleanup 118 -NumDeadlockRetries 518 -PollingInterval 6018 -QueryTimeout 40018 -SrcThreads 218 -StartQueueTimeout 018 -UploadGenerationsPerBatch 318 -UploadReadChangesPerBatch 10018 -UploadWriteChangesPerBatch 10018 -Validate 018 -ValidateInterval 60   Due to the memory leak issue with respect to replicating blobbed images we have changed UploadGenerationsPerBatch to = 3.

Transactional Replication: Agent Profiles

  
Can someone explain the different Agent profiles and when is it appropriate to use one over the other?  Agent profile, continue on data consistency error...when can this be used?

TX Replication Error: Agent set to verbose 2

  

Tx Replication is giving an error

Command attempted:

if @@trancount > 0 rollback tran
(Transaction sequence number: 0x00001E880000202E000800000000, Command ID: 1)

Error messages:

2010-09-16 20:10:17.543 Microsoft SQL Server Log Reader Agent 10.0.2531.0
2010-09-16 20:10:17.597 Copyright (c) 2008 Microsoft Corporation
2010-09-16 20:10:17.622 Microsoft SQL Server Replication Agent: logread
2010-09-16 20:10:17.647
2010-09-16 20:10:17.663 The timestamps prepended to the output lines are expressed in terms of UTC time.
2010-09-16 20:10:17.717 User-specified agent parameter values:
   -Publisher Server_A
   -PublisherDB db_A
   -Distributor Server_b
   -DistributorSecurityMode 1
   -Output C:\Users\xyz\Desktop\OUTPUTFILE.txt
   -Outputverboselevel 1
   -Continuous
   -XJOBID 0x052684F1D410C746B5AFE798220E5440
   -XJOBNAME Server_A-db_A-5
   -XSTEPID 2
   -XSUBSYSTEM LogReader
   -XSERVER Server_A
   -XCMDLINE 0
   -XCancelEventHandle 0000000000000960
   -XParentProcessHandle 00000000000009F0
2010

resource type SQL Server & SQL Server Agent missing after setup

  

Hello,

after the SQL setup I noticed that the resource types "SQL Server" and "SQL Server Agent" were missing. (one node setup, 2nd node was joined later) Well I was able to manually create them but they won't start. The OS is Server2008 R2 and SQL is SQL 2008 - NON R2, yet.

The resource "SQL Server" is in a failed state (please find the error message right below)

(An error occurred while attempting to bring the resource 'SQL Server ('instanceName')' online.Error Code: 0x8007139a
The cluster resource could not be brought online by the resource monitor).

"SQL Server Agent" is offline due to its dependency, the resource "SQL Server".

I already tried to repair the installation,  compared the properties of the 2 resources with a a working SQL2k8 cluster but with no success.

Does anyone have any idea what I could try next?

Thank you in advance

Masl

 

 

 


resource type SQL Server & SQL Server Agent missing after setup

  

Hello,

after the SQL setup I noticed that the resource types "SQL Server" and "SQL Server Agent" were missing. (one node setup, 2nd node was joined later) Well I was able to manually create them but they won't start. The OS is Server2008 R2 and SQL is SQL 2008 - NON R2, yet.

The resource "SQL Server" is in a failed state (please find the error message right below)

(An error occurred while attempting to bring the resource 'SQL Server ('instanceName')' online.Error Code: 0x8007139a
The cluster resource could not be brought online by the resource monitor).

"SQL Server Agent" is offline due to its dependency, the resource "SQL Server".

I already tried to repair the installation,  compared the properties of the 2 resources with a a working SQL2k8 cluster but with no success.

Does anyone have any idea what I could try next?

Thank you in advance

Emeska

 

 

 


Replication Distribution Agent: CXPACKET

  
I have a transactional replication that is growing in latency. The performance is Critical. Please guide how i can go about troubleshooting the problem. Please provider detailed steps. Thanks.

log reader agent stopped in transactional replication

  

hello frnds

I got this error in transactional replication in sql server

Error:The process could not execute 'sp_repldone/sp_replcounters' on 'FS001XSSQL110'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)

Get help: http://help/MSSQL_REPL20011

The log scan number (54862:18189:10) passed to log scan in database 'Affinity' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. (Source: MSSQLServer, Error number: 9003)

Get help: http://help/9003

The process could not set the last distributed transaction. (Source: MSSQL_REPL, Error number: MSSQL_REPL22017)

Get help: http://help/MSSQL_REPL22017

The process could not execute 'sp_repldone/sp_replcounters' on 'FS001XSSQL110'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)

Get help: http://help/MSSQL_REPL22037

this is what i am getting when i viewed the log reader agent in replication monitor.

Thanks


dimrd_SQL

Merge replication setup with SQL EXPRESS 2005 on Windows 7 Professional

  

Hi all,

I have a web app that runs on local and use merge replcation using sql server 2005 standard on the server and sql express 2005 on clients on XP. As you know, XP Pro laptops are getting hard to find. We are trying to change to Windows 7 Pro x64. I installed SQL Express 2005 and I don't see a subscription on "Sync Center" after I created local subscription using SSMS. I normally see the subscription in Synchronize in XP Pro right away. 

I googled about this issue and not really have a good solution. There is one link saying Windows 7 not supporting Express 2005 anymore. http://blogs.msdn.com/b/repltalk/archive/2010/03/24/using-windows-synchronization-manager-on-x64-to-synchronize-replication-revised.aspx 

If so, I would like to know what would be a solution such as can I use Sql Express 2008 R2 instead of Sql Express 2005 for client even if the server is still SQL Server 2005 Standard edition. We are planning to upgrade, but we need to hire 5 to 10 people now. My boss does not want us to keep using XP Pro. 

Any suggestion would be appreciated.

Thanks,

Sompop



Replication Setup Error

  

Hello,

I'm setting up replicaiton between two MS SQL 2008 servers and I'm having issues getting the snapshop at the publisher to work.  I get the following message:

 The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.

I have created a windows account on the network, provided that account with admin rights and I have changed agent to use this account to run.  Repldata has been shared and I provied that created account with full rights to that folder.  That account also has the db_owner rights on the DB that I am trying to replicate. 

Am I missing a step? What might be the issue here?

 

Thanks.


SQL DMO/SMO Replication setup SQL 2005, 2008, 2008 R2

  

I have a VB.NET program that uses SQL DMO to setup the SQL Server for replication, create the publication with all the articles and start the snapshot creation. With SQL 2008 R2, DMO is unavailable (at least with SQL 2008 there was a backwards compatibility package that i could load to get it).

I have read that SMO was available in SQL 2000-2005 and i know there were some differences, but i am only using it for the replication setup. Then i saw some in the BOM about RMO.

I am a little confused about the RMO - is that just a sub-set of SMO?

My BIGGEST concern is that i write something and it works perfectly on R2 but fails on 2008 or 2005 (since we still have customers using those versions).

Can anyone point me somewhere that talks about changing from DMO replication setup to SMO/RMO.

Thanks.


SQL 2008. Merge replication. Snapshot agent. Access Denied

  
Windows Server 2008 Standard x64 SP1, SQL Server 2008 Enterprise Edition x64 SP1
Snapshot agent has read-write permissions to ReplData folder but cannot access local snapshot folder. How to resolve this error?

Error messages:
Source: mscorlib
Target Site: Void WinIOError(Int32, System.String)
Message: Access to the path 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\ReplData\unc\ServerName_DatabaseName_PublicationName\DateTime\' is denied.
Stack:    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, DirectorySecurity dirSecurity)
   at System.IO.Directory.CreateDirectory(String path, DirectorySecurity directorySecurity)
   at Microsoft.SqlServer.Replication.Utilities.CreateDirectoryWithExtendedErrorInformation(String directory)
   at Microsoft.SqlServer.Replication.Snapshot.SnapshotProvider.CreateSnapshotFolders()
   at Microsoft.SqlServer.Replication.Snapshot.MergeSnapshotProvider.CreateSnapshotFolders()
   at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot()
   at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun()
   at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: mscorlib, Error number: 0)
Get help: http

Sybase to SQL Server Replication setup

  

Dear Tech experts,

Currently we have customers extensively using online replication between their production , BCP and reporting servers. We have to provide a similar replication toppology in the SQL Server 2008 environment. With a sequenced rollout of applicaitons across their business units, there will be coexistence of Sybase and SQL Server platforms (heterogeneous replication).

Pls guide us with relevant links/info on this along with your comments


How should be the Replication agent privileges ?

  
I'm going to setup the transactional replication in sql server 2008.and publisher ,distributer and subscriber are going to place on different servers. I want to know, how should be the privileges for sql agents for all servers?Is any custom important setting when we install the sql server for distributor ?

How should be the Replication agent privileges ?

  
I'm going to setup the replication in sql server 2008.and publisher ,distributor and subscriber are going to place on different servers. I want to know, how should be the privileges for sql agents for all servers?Is any custom important setting when we install the sql server for distributor ?

Replication Log Reader Agent Error - No Information

  

SQL Server 2005 SP3, I have created an Oracle Publication for transactional replication.  All seems to be working, even getting transaction updates from Oracle. In replication monitor Log Reader Agent status is "Error".  Last action is "applying retries....".  When I view details, window is empty - though once before (when I saw details), details told me to check job history.  Job history shows - "The replication agent encountered an error and is set to restart within the job step retry interval. See the previous job step history message or Replication Monitor for more information."

I understand that the Log Reader is moving data change info to distribution and it seems important to understand the errors.  The Log Reader agent is using the SQL Agent Service Account.

Log Reader Agent profile properties are default.

Here are details of error:

Details in job step message:

Date  10/29/2010 11:23:54 AM
Log  Job History (PULPDEV-PULPDEV-19)

Step ID  2
Server  WAFEDASDM10
Job Name  PULPDEV-PULPDEV-19
Step Name  Run agent.
Duration  01:06:07
Sql Severity  0
Sql Message ID  0
Operator Emailed  
Operator Net sent  
Opera

The best way to prevent an agent job to run in the middle of a merge replication.

  

Hi,

I would like to configure a SQL agent job such that it doesn’t run in the middle of merge replication synchronization. Means when a merge replication is taking place, the job have to wait, or just run again until merge replication is done.

What would be the best way to do this?

Thank you.


Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend