I would like to setup replication between production server and a development server. At the same time, I would like to be able to add a row of data to the development server and not have that data overwritten when the replication takes place.
Is there a way to accomplish this?
On one particular subscriber (out of 40+), an error was throw that there were no available identity ranges. In debugging, it was found that this particular subscriber had allocated ranges for all articles 800+ times over the course of a few days by examining msmerge_identity_range_allocations thereby using all int values.
I'm trying to figure out why this happened. Perhaps since all articles for this publication exhibited this issue, the subscription was marked for reinitialization and it was never able to complete but allocated new ranges for the articles and didn't remove those allocations upon not being able to complete all actions. There do not seem to be any hints in the SQL Error logs to help my debugging process.
Has anyone else seen an issue like this? If so, how did you correct it or at least determine root cause?
Hi All,
Current scenario: Site 1 (Publisher DB) --> Site 2 (SubscriberDB) -- Transactional replication is setup
Now,we need to add another subscriber at Site 3.
We plan to initialize the 2nd subscriber using a Backup. (http://msdn.microsoft.com/en-us/library/ms151705(v=sql.90).aspx). Currently, allow_initialize_from_backup is
already set to 1.
While adding new subscriber, I plan to DISABLE DISTRIBUTOR CLEANUP JOB temporarily to prevent removal of transactions from the distribution database.
Further, we need to setup a filtered replication from this 2nd subscriber.
Questions:
1. Is there a downtime (even a small one) needed during this initialization using backup?
2. What other risks are seen during this kind of setup?
3. If I use the steps at http://msdn.microsoft.com/en-us/library/ms147834(v=sql.90).aspx to add the subscriber,
it will by default create a push replication, am I correct? (as that is what I want)
any help is highly appreciated!!
Thanks.
What has been people's experience doing this?
What special changes to Transaction replication Publication or Subscriptions are required?
Any contra-Indications?
Thanks
...Ray
...Ray
hello,
We are looking to set-up replication for our main database and was after some advice on what might and might not work. We are using SQL Server 2008 R2 standard.
The database is around 130gig in size and the main data table has around 600million rows. This table has many changes in both updated and additions (I would guess up to 200k updated/additions a day). It is expected that the database will continue to grow more rapidly in the future.
We have a remote site that we want to replicate to and our connection to the site is a site-to-site vpn with about a 4meg bandwidth.
The dream setup would be to put in place two-way replication where both databases are editable and I can choose to use either database. The performance of the Master database could not afford to be significantly impacted while the secondary performance would not be as critical. It would also be good if whatever setup is used could be later expanded to include additional target sites.
Based on the very little information that I have provided can some provide advice on 1. is this possible and 2. what is the best technologies and setup that I would likely be used.
matvdl
Hi,
Can anybody tell me the fail-over procedure in all types of replications?
For example: if Publisher/Distributor/subscriber is down?
Hi,
am getting this error, after replication is completed.....
launch repliction monitor
Cannot open database "text" requested by the login. The login failed. (Source: MSSQLServer, Error number: 4060)
Get help: http://help/4060
will do the transactional replications.
Regards,
Abdul Khadir
Basically i want to add articles to existing subscriber without taking entire snapshot
Code i am using to add articles to subscriber
EXEC sp_changepublication
@publication = 'Transaction_replication',
@property = N'allow_anonymous',
@value = 'false'
GO
EXEC sp_changepublication
@publication = 'Tranasaction_replication',
@property = N'immediate_sync',
@value = 'false'
GO
EXEC sp_addarticle
@publication = 'Transaction_replication',
@article = 'table1',
@source_object = 'table1',
@force_invalidate_snapshot=1
----- Till this no errors..after i execute below script i am getting error-----
EXEC sp_addsubscription
@publication = 'Transaction_replication',
@subscriber = 'subscriber_servername',
@destination_db = 'subscriber_dbname',
@article = 'table1',
@reserved='Internal'
-----Error----------
Msg 14278, Level 16, State 1, Procedure sp_verify_schedule, Line 292
The schedule for this job is invalid (reason: @freq_recurrence_factor must be at least 1.).
Msg 14070, Level 16, State 1, Procedure sp_MSrepl_changesubstatus, Line 1208
Could not update the distribution database subscription table. The subscription status could not be changed.
Msg 14057, Level 16, State 1, Procedure sp_MSrepl_addsubscription_article, Line 383
The subscription could not be created.
Regards,
Satish
We have a merge replication between 2 servers. We will have a maintenance on one server and would like to stop all the replications. How to stop it? Do I need to stop the SQL agent?
Recently we encounter some errors on the log reader agent job for all our publishers in our push replication setup. All publisher dbs are coming from the same db in the publishing server. Our distribution db is on its own physical box. We are using SQL 2008 r2. The first error is related to“The process could not execute 'sp_replcmds' . The second one is "Could not obtain information about Windows NT group/user 'domain\xxxxxx', error code 0x5”. The strange thing about the second error is that we don't use that account to set up the replication. I am using a totally different account for it. Just in case, I checked all log reader security set up for the publisher dbs and it is using the sql job agent account by impresonation and not using the said domain account in the error. Another interesting about this problem is that the problem would self-correct meaning after a few hours of giving out the errors, the log reader would function again and distributing the commands to the distrbution db.
I need to find out why the replication is giving out an error on a domain account that we don't use. A little bit of background info here. We did move all our servers to a different location and set up a new domain for everything. However, all replication setup started from scratch so there is no chance I would use the said account to set up my replication. the only thing that is coming from the old location (or old domain) is the databases. We did a backup and restore to bring the databases to the new location but we don't restore the original publisher settings during the restore.
Is it possible that somehow there is some old replication setting related to the said domain account somewhere in our current replication setup somewhere? Is there a command I can use to search for this domain account in our replication setup? Any ideas or thoughts are very much appreciated.
od
Ocean Deep
I have Replicated live database 'db1' from server 1 to database 'db2' of server 2. It got replicated correctly.
But when i restored that replicated database to 'db2' to one more database called 'db3' in server 2,it gives the 'Duplicate key error when using the database to insert data to db3.i even tried reseeding the identity primary key of every table to the max
of that column still that error persists.can give me a solution???
Hi All,
we have a transactional replication , suddenly subscriber database was down... on that time my distribution database size was grow irregular , i have try to shrink the distribution database size and tacking the log backup also but it's not working .. still distribution database size was growing .
currently subscriber database was up and running fine but still i am facing the above problem.
In this situation how to troubleshoot the issue?
please post the your valuable posts on this ASAP.
Thanks in Advance
RAM
We have configured the distributor on SQL Server 2012 and we were able to create a publication on another server running SQL 2008 R2 until recently. Now were getting this error message when we tried to configure the remote distributor on the publication server. NOTE: the password is correct and has been doubled checked.
We are replication 2008 db to 2012 instance. - Thanks Norm
Title: Configuration Distribution Wizard
SQL Server could not connect to the Distributor using the specified password.
Connection to server failed.
OLE DB provider "SQLNCLI10" for linked server returned message "Login timeout expired".
OLE DB Provider "SQLNCLI10" for linked server returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information.......
Hi,
I'm working on SQL 2012. My OS is Windows 2008. When I created a publication for a replication transaction, snapshot agent failed as below error:
"A .NET Framework error occurred during execution of user-defined routine or aggregate "sp_scriptdropinsreconciliationproc_sqlclr":
System.TypeInitializationException: The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception. ---
".
Could you help me to resolve this issue ?
Thanks
Hi
How to view and store the changed records in the transaction or merge replication?
Much Thanks
Hi All,
I have faced issue regarding stored procedure.
actually my application team ran the stored procedure regular basics (contain some inserts) ,,every day it take 20 mins for executing but today it's tacking the more than 2 hours (still it's running) .
i have checked the which they are inserting and ran the updated statics also,i have checked and fixed the table fragmentation and indexes related issues but still it's tacking the logtime for executing .
what is the recompile ?
how to resolve the slow running stored procedure?
Please post the your valuable ANS ASAP.
Thanks in Advance.
RAM
Hi Team,
I have changed the password of distributor_admin account manually and now all my snapshot replicaton jobs are getting failed in distributor server with below error.
10:23:18.02 Source: Replication
10:23:18.02 Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentSqlException
10:23:18.02 Exception Message:Login failed for user 'distributor_admin'.
10:23:18.02 Message Code: 18456
Without doing snapshot creation I want to do transactional replication.
How it is possible.
Thanks
