i have one dought
publisher is 2008 subscriber is 2000 data will be published or not
because we are going to configure this t-replication. suggest me.
View Complete Post
I have windows 2003 sp2 servers each hosts SQL Server 2008 SP1 standard edition. I am trying to replicate both servers, using the tutorial available in the online documentation <Tutorial: Replicating Data Between Continuously Connected Servers> which
can be found at: ms-help://MS.SQLCC.v10/MS.SQLSVR.v10.en/s10rp_1devconc/html/9c55aa3c-4664-41fc-943f-e817c31aad5e.htm
I have created the users (repl_logreader, repl_distibution, repl_snapshot, and repl_merge and setting their security. Then I have created the distibutor, setting database security as mentioned in the document, and last creating the publication with a snapshot
to be run immediately, distributor and publisher are on the same server and the publication will be pushed to the subscriber. Once the publication is created succesfully, I am checking the agents to see the errors. I am always stuck with the following two
1- snapshot agent error:
Message: Failed to create AppDomain "mssqlsystemresource.dbo[runtime].1090".
The domain manager specified by the host could not be instantiated.
Failed to create AppDomain "mssqlsystemresource.dbo[runtime].1091".
The domain manager sp
i want to know how to reslove conflicts when using Bi-directional transactional replication ,,conflicts like
1-If you insert a record that has a key into a table on one of the servers and another record that has the same key already exists on the other servers that participate in the replication, the replication does not propagate the changes to the other servers.
2-When you update a column in a record that is updated at the same time on another server, the data may be different on the two servers.
3-When you update different columns in a record, simultaneous updates of different columns of a record may sometimes lead to conflicts.
4-When you delete a row that is being deleted at the same time on another server that is participating in the replication, the replication fails because the DELETE statement does not affect any rows on some of the subscribers.
..i need help to know what to do to handle this conflicts and if there is any implementation or any ideas about this issue
I have a primary database replicated to another server where I have added legacy data to the subscription.
1.Can i perform Tx Log shipping of this subscription to another server?
2. Republishing of the subscriber was very hard to maintain and throws errors when ever the servers involved are restarted. Can Log shipping help in this respect?
3. Question: Can we add static data to the subscriber when using LOG shipping? Thanks
The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "REPL1 " was unable to begin a distributed transaction. Changed database context to 'database1'.
I'm using transactional replication only for reporting purpose (DB1 (publisher) ->DB2 (Subscriber).For Some function really on the latency time to select data from DB2.That mean When user click one button it will update in DB1 first then by the changes
it will read from DB2.So now I have hard code the wait time to read from DB2 after update in DB1.What is the correct way to solve the problem. Is any way to get the latency time from Distributor from code behind?
Recently we have moved our Primary DB system from SQL 2005 single Instance Running on windows 2003 to SQL 2008 2 Node Cluster Running on Windows Server 2008.
Server Config as below:
HP DL380 G6, 2*4 Xeon X5550 2.67 GHz with 44GB Ram running SQL Server Standard Edition. Connect to HP MSA 2012FC - Dedicated SAN.
Hyper threading is disabled.
We have transaction replication configured from the Primary DB server to 2 subscribers and from there to 8 Different Servers.
We have a transactional replication database where in we have set the schema change property to false. Now we have added a new column and to the table and wanted this column also to be replicated. But before enabling the allow schema replication parameter,
we have altered the article added a column.
Now we reliazed that we have not enabled the sehema replication option. The database is very large and reinitializing the subscription remains our last option.
Could anyone suggest us the right way forward.
Thanks in advance.
In short, can replication cause a transaction log file to grow and not be shrinkable? Specifically:
My database (now SQL 2005) had done fine for several years. The transaction log would occasionally get too large, and I'd back it up and shrink it. The "initial size" was something less than 10 MB, and so the file could shrink to a small size.
A few months ago I set up the database as a publisher and a distributor to replicate to another server. It's a snapshot push replication (runs continiuously, replicates once daily). I think it's around that time that the transaction log
starting growing significantly, and the "initial size" increased. Now the "initial size" is around 12 GB, over 1000 times larger than the actual original "initial size". Since SQL doesn't allow the transaction log file to decrease in size less
than the "initial size", it won't shrink. It doesn't seem good to have an MDF size of 3 GB and an LDF size of 13 GB.
I tried many things to resolve this, and got help from another Microsoft SQL forum, but no solution.
When I run dbcc shrinkfile, it generates the message "Cannot shrink log file ... because all logical log files are in use". Is it possible that the replication is what's keeping the logical log file
Hi Team, In transaction replication in Publication database i want add one column on one article how can i add col in the article. (we need to add constraint not null also )
(we need to how can we update this new column in subscriber database through distribution same article please guide me..(Transaction Replication) Thanks in advance... tx
Please any one how have information if that the SQL server 2005 transaction replication require windows server Enterprise Edition, is that right on not ?
Sorry I am kinda new in web services, so it may sound a bit newbish question.
We have a web service that comunicates with the database and exposes web methods that enables the application to access the database. Each method does only one operation (Insert, Update or Delete). What I need to do is create a transaction that will be consisted of multiple calls to the database, meaning multiple calls of more then one web methods. Can I do that? (I read that if the web method does not throw exception - or ContextUtil.SetAbort() is not called - the transaction will be commited automatically when the web method finishes executing, which I don't want to happen because I want to call another web method in the same transaction, and then manually commit the transaction)
Thank you in advance.
MSDN Magazine May 2007
This article presents a general-purpose client quality reporting mechanism that can be used in any .NET-based transaction system that employs HTTP/SOAP. The design uses client response time and quality recording, upload of logs as SOAP headers attached to new transaction requests, and server handoff of these headers to a low priority queue for logging and analysis. This technique gives an enterprise near real-time information on actual end-user response times. These response times reflect network delays, client application overhead and server delays. By using this technique, enterprises can avoid the need to develop custom software to mine HTTP logs.
MSDN Magazine July 2004