Hi All,
I am able to successfully launch replication monitor, but I couldn't see the publications under the publisher. As i already mentioned in the subject line , it shows up up small red mark crossed. My Colleagues are able to see the publications of the same publisher . I am a 'SysAdmin' , but still i am not sure , what is the problem . Please help me to resolve this issue.
Regards
Chaithanya M
Regards Chaithu.. If it is usefull,Mark this as Answer.
Hi,
I'm in need of moving the database files to a different drive. Well I can't because 1 of the databases is replicated. (when you right click on the database to click detach, there's a message that says database replicated and it cannot be detached).
So upon investigating, I looked under the Replication Folder and saw 5 local publications and 2 local subscriptions setup. I also went to the Publisher Properties underneath the Replication folder. Under Publication Databases, the one that is replicated is checked for transactional.
My question is what is the best way to break the replication so I can move the MDFs and LDFs to the new drive and then reattach them and restore replication?
Could I just uncheck the Transactional check under Publisher Properties --> Publication Databases and then to my detach and re-attach? Then go back under replication and check the database to be transaction again and everything be fine?
Or is there more to it than that? Do I need to do anything with deleting and recreating the Local Publications and Subscriptions?
JB
Hi,
I use MY snapshot job for a publication,
When I call sp_addpublication_snapshot I specify @snapshot_job_name.
In the job I have already configured the scheduling time for the snapshot.
Do I need to specify the scheduling parameters ( @frequency_subday,@frequency_subday_interval, @frequency_relative_interval,@frequency_recurrence_factor, @active_start_date,@active_end_date , @active_end_time_of_day....) again ?
Will they overwrride the job definishion ?
If I ignore them , what will happen ?
Regards, Asi Pesa
I am trying to deploy my vb.net application to Windows 7/8 environment which has SQL2012 Express installed on it.
All works fine until I try to use Merge Replication. I get the following message -
System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {1E6ADC03-1A05-4DF0-B627-3DAE0F6DA188} failed due to the following error: 80040154.
In have rebuilt and re-deployed the app using X86,X64 or Any CPU as the platform - all to No avail.
Is there anything special I have to do with the InterOp.sqlmerg.dll file
david
Hi,
where the replication snapshots will be located?
Hi,
In the documentation on the procedure sp_addpushsubscription_agent it says " to synchronize a push subscription to a transactional publication". It doesn't refer to snapshot replication at all.
As I understand this procedure creates the distribution agent .
The distribution agent is used in snapshot transaction as well (to push the snapshot)
If I'm creating snapshot replication , should I call sp_addpushsubscription_agent ?
Regards, Asi Pesa
HI,
Can any one pls tell how queue reader agent works in replication, how we can observe whether it is working fine or not?
Hi,
How to identify conflict between duplicate in transactional replication?
Hi,
In replication where do we find the issues related to repicated databases or from where we get to know that transactions that not affected from publisher to subscriber.
Hi All,
we have configured transaction replication ,publication database is created in subscription but tables are not showing in subscription database.
Hi
I have a merge replication between SQL Server 2005 (Publisher), and multiple SQl Compact Database (Subscriber),which was working fine, suddenly it stopped working and throwing the error message the below error messages
1) 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.
2) The merge process could not enumerate changes at the 'Publisher'. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write
So I just restarted the SQL Server Agents, and dropped the Merge replication using the below commands
sp_removedbreplication 'dbname' EXEC sp_dboption 'dbname','published’, false
Then I started to create the Merge replication using the new publication wizard with the merge publication type and added the 2 articles to the publication and clicked finish
It is throwing the error
Invalid object name 'sysarticles'. (find down the picture inserted for more detail.
So I unable to the create the merge replication.
Anyone can help me out to figure out why this error message occurs?
Srikanth[096]
In a transactional replication, when we are re-initializing the subscription the snapshot agent results in error.
"Failed to initialize the Common Language Runtime (CLR) v2.0.50727 due to memory pressure. This is probably due to memory pressure in the MemToLeave region of memory. For more information, see the CLR integration documentation in SQL Server Books Online."
SQL Version- SQL Server 2008
It is a 32 bit machine and AWE /3G is not enabled. There are no CLR objects in the server.
Please advice on this.
Thanks
Hi All
I have a publisher server It is replicating to 3 subscribers.I want to offline one database. Can we offline the database without breaking replication? If not, what is the best or easier way to do so we don’t have to setup replication again. Please advise.
All SQL Servers versions are SQL Server 2008R2
We are looking at various HA options and have decided upon SAN replication between our two Data centres in two separate domains. We are SAN replicating all production databases but not system databases.
At the same time we need to replicate production data using Transactional Replication from the primary data centre through a remote distributor to the subscriber in a third data centre. I would like to configure our transactional replication so that the log readers are able to handle a fail over from the primary data centre to the secondary data centre without having to drop and recreate replication.
Because SQL Server replication is so tightly knit with SQL Server Servername\Instance names I've created the same SQL Server named instances at both data centres.
In theory is all this possible? If not is there anything else which I can try to achieve the same results?
I am new to SQL Server, but am quick to learn and I know where to find answers. However, I have found this issue on this and other forums and I have tried the solutions and am still getting a failure. This is the following error I get:
The schema script 'ap_OnePermissidbf20687_253.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001
Invalid column name 'CompanyID'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
It appears that the tables and views and everything are copying over, but I am never able to get a full sync done without running into these errors.
To give a quick background, we have two newly built SQL servers that I restored a backup of another database onto the Distributor/Publisher server. I have gone through the Distribution Wizard and Publication wizard and the snapshot creates with no issues. I have set the Replication location as a shared UNC name and can access it from another terminal using the log in that I am using for the process login.
Any help is greatly appreciated as I have been slamming my head against this same wall for over a week now. If any more info is needed I would be happy to supply that.
Thanks,
Robert
Hello Experts,
I need help in SQL Server 2008 R2 Enterprise Edition while doing Log Shipping.
After Completion of all procedure of the Log shipping. I get the error in Copy Job in Secondary Database Server.
Error is "Executed as user : server name The Step Failed."
Thank You in Advance.
Warm Regards,
Dhaval Dave
Hi,
I am searching for an explanation of a replication snapshot being in excess of 5 times what we're predicting
Following a replication failure we are attempting to reinitialise subscriptions with a new snapshot. The size of the database is 135GB, one table within the database is 60GB - we have excluded this article from the publication. This meant we had an expectation of snapshot size being ~75GB.
We've had several attempts at creating the snapshot and these have failed due to lack of disk space. Last night the snapshot filled a disk with 340GB of free space.
I 'd welcome any explanation for this huge size of snapshot.
In my examination of possible causes I note that the snapshot format is set to "Character - Required if a publisher or subscriber is not running SQL Server". This despite the fact that at both ends of this transnational replication is native SQL Server. Is there a different in size between formats?
Thanks in advance.
I have got below error on copy database wizard.
Date9/19/2013 2:00:00 PM
LogJob History (CDW_TESTING_SQL2008_SYS13_SYS13_14)
Step ID1
ServerSYS13\SYS13
Job NameCDW_-TESTING_SQL2008_SYS13_SYS13_14
Step NameCDW_-TESTING_SQL2008_SYS13_SYS13_14_Step
Duration00:00:13
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0
Message
Executed as user: SYS13\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.50.4000.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 14:00:00 Progress: 2013-09-19 14:00:01.98 Source: TESTING_SQL2008_SYS13_SYS13_Transfer Objects Task Task just started the execution.: 0% complete End Progress Error: 2013-09-19 14:00:11.32 Code: 0x00000000 Source: TESTING_SQL2008_SYS13_SYS13_Transfer
Objects Task Description: An exception occurred while executing a Transact-SQL statement or batch. StackTrace: at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes
executionType) at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(StringCollection sqlCommands, ExecutionTypes executionType) at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.CreateObject(String
database, StringCollection script) at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.TransferJobs(DatabaseObject dbObject) InnerException-->The specified '@notify_email_operator_name' is invalid (valid values are
returned by sp_help_operator). StackTrace: at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException) at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String
sqlCommand, ExecutionTypes executionType) End Error Progress: 2013-09-19 14:00:11.33 Source: -TESTING_SQL2008_SYS13_SYS13_Transfer Objects Task Database transfer failed for one or more extra objects.: 0% complete End Progress Progress: 2013-09-19 14:00:11.33 Source: testingserver_SQL2008_SYS13_SYS13_Transfer Objects Task Transfer objects finished execution.: 100% complete End Progress Warning: 2013-09-19 14:00:11.34 Code: 0x80019002 Source: CDW_TESTING_SQL2008_SYS13_SYS13_14 Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the
maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning DTExec: The package execution returned DTSER_FAILURE
(1). Started: 14:00:00 Finished: 14:00:11 Elapsed: 10.749 seconds. The package execution failed. The step failed.
Akshay Pate Server Administrator
