SQL2000 Replication Deadlocks

We have an SQL2000 database server that uses merge, pull replication with about 70 clients around the country, each with their own publication.  Each article in each publication is row filtered by a single condition.  There are busy times of the day when all of these clients attempt to replicate within a 15-20 minute period.  We have noticed the following error that is creating conflicts that are resulting in data not being transferred to the server and very long replication run times (error message is paraphrased):

 

The record was inserted at the client, but could not be inserted at the server.  Transaction (Process ID XXX) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.  Rerun the transaction.

 

Is there a way to lessen the effects of this error?  How can I reduce the number of deadlocks that are occurring?  We will need to be adding a great deal more clients to the system in the future;  is there a way to grow the system without making the deadlock problem worse?

 

Any help will be appreciated!

 

Thanks,

Craig

 

 

View Replies


ADVERTISEMENT

Replication Deadlocks

Hi All,

View Replies View Related

Snapshot Replication Deadlocks

Is there anyway to prevent deadlocks during the snapshot replication?

I understand that you can minimize by maybe creating a couple different snapshots (mixing tables to minimize locking while snapshot is being created), but is there any other way?

Thank you

View Replies View Related

Sql2000 Replication

hello,also wanted to confirm which versions of sql2000 can do replication.Would be nice to have fault-tolerance via replication so as to have ahot-standby.Oskar

View Replies View Related

SQL2000, SQL 7 And Replication

I have SQL 7 publishers, a SQL7 Distributor and I want to create a SQL2000 subscriber. Can this be done? Or do I have to make a SQL2000 Distributor too? Any thoughts would be appreciated.

View Replies View Related

Replication Between SQL7 And SQL2000?

Guys, we want to use the Replication features (or something similar) tobackup our primary SQL database, the primary DB is using SQL 7 and oursecondary server is SQL 2000 - is this possible?p.s. I know it would be more suited to use the SQL2000 server as theprimary, but thats a later plan...Appreciate your helpCheers, @sh

View Replies View Related

Replication SQL2000 To DB2 V8.1 Express

Hi,
Any body successfully implemented Replication from SQL2000 to DB2 V8.1 Express?
FYI, I successfully implemented replication from SQL2000 to DB2 UDB V7.2 thru Microsoft OLE DB driver last year, but the same method I use hit error when replicating to DB2 V8.1 Express. I can succeffully create the link server from SQL2000 to DB2 V8.1, but when I list DB2 tables from SQL Enterprise Server (GUI), it give me

Error 7330-Could not fetch a row from OLE DB provider 'UNKNOWN'.
OLE DB error trace[OLE/DB Provider 'UNKNOWN' IRowset::GetNextRows returned 0x80040e14]

View Replies View Related

Replication SQL2000 To MySQl

Hello Guys,

I'm trying to configure a Transactional Replication from SQL 2000 to MySql using MyODBC.

The problem:

When I try to add a new Subscriber, I receive the following message:

'ODBCMYSQL' could not be enabled as a subscriber because the ODBC driver for this data source does not provide sufficient functionality. Contact the vendor to obtain an updated ODBC Driver.

Error 2132: [SQL-DMO]The DSN is not a valid SQL Server Subscriber

View Replies View Related

Replication Access / SQL2000

Hi,

I made an application in access 2000 and I use the internet replication.

I got the replication manager installed on the same server with SQL2000 server.

What I Would like to do is replication between SQL2000 and Access database.

Is it possible to make replication between Access database and SQLServer, and is it possible to make it work in bi-directionnal mode ? cause change can occur in both database (Sql and access).

Thanks for the help

Richard

View Replies View Related

Replication Between SQL2000 And SQL2005

I have a distributor setup on SQL Server 2005 (9.0.3042) and am trying to create a publication on SQL Server 2000 (8.0.2040) which receives the following error in my production environment:
 

Msg 8526, Level 16, State 2, Procedure sp_addpublication, Line 802

Cannot go remote while the session is enlisted in a distributed transaction that has an active savepoint.
 
The interesting part of this equation is that I was able to get this to work without error in my DEV (development) environment and well as my QAT (test) environment.  This end result was that my distributor was SQL 2005, my publisher was SQL 2000 and my pull subscriber was SQL 2005.  I have been diligently comparing our production environment to my other environment and have yet to find differences.
 
Has anyone else seen an error similiar to this?  Any insight would be appreciated.
 
Thanks in advance,
 
Max

View Replies View Related

Replication From SQL2000 To SQL2005

I want to replicate from SQL2000 to SQL2005. I had configured distributor, publisher in SQL2000 and also subscriber in SQL2005. But so far no replication was done on SQL2005. I wonder SQL2000 (SP2) and SQL2005 replication will it work? Is it true that I should install Service Pack 3 and above in order to replicate my database to SQL2005.
 
Thanks
Wint

View Replies View Related

SQL2000 And MSDE Desktop Replication

Greetings all,

I am planning a sales automation app and needing to synchronize data to salesmen whose machines are not always online. What we've had in mind was to use our SQL Server 2000 and its' built in replication functions and possibly replicate to the MSDE SQL desktop engine on the salesmens' machines. What would be the best replication type for that? Transactional, Snapshot or Merge? Has anyone done anything similar to this? The data will originate on an AS/400 Midrange iSeries box and be replicated to the SQL 2000 box using a product such as Vision Solutions' Sybiator. From there around 15 tables will be replicated to the MSDE, each with an average of 5,000 records, though a few with 70-80k. I'm not worried about collecting data back from the salesman MSDE at this point. This is a one way replication from our SQL to the subscribers.. ANy advice or warning would be appreciated. (If someone would just like to say it's a dumb idea, that's great, too!)

Bill

View Replies View Related

Replication Between Sql2000 And Access 2000

Hi,

It is possible to do a bi-directionnal replication between access 2000 database and SQL server (Access and SQL server are on the same server)

What is the better way to do it.

For info, i use the SQL for the web part but access is used for an application in vab/access. Data have to be synch all the time.

Thanks for the help

Richard

View Replies View Related

SQL2000 Server And MSDE Replication

 Hello.

I will construct client application with MSDE.

I face with a difficult question.

It's in sync with SQL2000 Server  and MSDE.

Client number is 5000.

I fall in a dilemma. Which do i use,  Replication or to make DB Sync application ?

jongwoo

 

 

 

 

View Replies View Related

SQL2000 Replication,modifying The Width Of A Column

Hi All,
Is there a way by which we can modify the width of a column of a table which is being replicated without touching the ongoing transactional replication? This is for MSSQL2000 Transactional Replication.

I know (and successfully tried) that we can add a column to a table and that gets propaged to the replicate database and indeed the added column gets reflected there. How to add a column? sp_repaddcolumn or Right Click on the Publication-Properties and it shows a button to Add a Column.

This is what I have tried for modifying the width of a column of a table participating in Transactional Replication from varchar(10) to varchar(100)

MH (source) -> MH1 (Replicate)

The column “col1” had width of varchar(10) and this was altered to varchar(100).


insert into MH..test_mh values(4,'abcdeabcdefff')

select * from MH1..test_mh

exec sp_dropsubscription @publication = N'MH', @article = N'test_mh', @subscriber = N'UKPBDRMTST2', @destination_db = N'MH1'
go

exec sp_droparticle @publication = N'MH', @article = N'test_mh'
go

alter table test_mh alter column col2 varchar(100) null OR

MH1..sp_help test_mh

exec sp_addarticle @publication = N'MH', @article = N'test_mh', @source_table = N'test_mh'
go

exec sp_addsubscription @publication = N'MH', @article = N'test_mh', @subscriber = N'UKPBDRMTST2' , @destination_db = N'MH1'
go


Needless to say, help would be apreciated -:)
~Mihir


However, adding a column was possible.

View Replies View Related

Merge Replication SQL2000 Error 2812

Hi !

When trying to start a Merge Replication agent I get the following Error message:

The process could not enumerate the changes at the subscriber. 2812

The snapshot agent works fine as far as I can see.

The replication is set up between a Win2000 / SQL7 / SP 4 and a Win2003 / SQL2000 / SP 3a machine. Sqlserveragent on both machines is run as a system account.

Any tip is welcome!

Thanks
VincentJS

View Replies View Related

SQL7/SQL2000 Replication. Auth Error

I'm attemting to replicate from a SQL7 box to SQL2000.

The snapshot works fine, but it fails when it tries to push the subscription to the SQL2000 box with a trust error (I don't recall the exact message). I noticed that it fails when Enterprise Mgr is configured as: "Tools/Replication/Configure Publishing, Subscribers and Distribution", Subscriber Tab, "Impersonating SQL Service Agent". It works if I change to "SA".

This is only the case when we replicate from SQL7 to SQL2K. SQL7 to SQL7 works fine with "Impersonating". Has anybody seen this behavior? Any workarounds, other than using SA?

View Replies View Related

SQL7/SQL2000 Replication. Auth Error

I'm attemting to replicate from a SQL7 box to SQL2000.

The snapshot works fine, but it fails when it tries to push the subscription to the SQL2000 box with a trust error (I don't recall the exact message). I noticed that it fails when Enterprise Mgr is configured as: "Tools/Replication/Configure Publishing, Subscribers and Distribution", Subscriber Tab, "Impersonating SQL Service Agent". It works if I change to "SA".

This is only the case when we replicate from SQL7 to SQL2K. SQL7 to SQL7 works fine with "Impersonating". Has anybody seen this behavior? Any workarounds, other than using SA?

View Replies View Related

Do I Really Need A Snapshot (to Initialize Transactional Replication, In SQL2000)?

I have a pretty big (350 gb) OLTP database that I want to replicate in its entirety.  I'm concerned about the impact of taking a snapshot of it (it is processing at some level pretty much 24x7).  I know on SQL2005 there is the option to initialize from backup, but unfortunately we won't be on 2005 in time.

I'm thinking of doing something like this:

Set up the distributor, publication, and subscription
Turn off distribution agent
Set the publisher to "sync with backup"
Backup the publisher, full then log
Truncate tables MSrepl_transactions and MSrepl_commands in the distribution db (I don't have any other replication going on)
Turn off "sync with backup"
Restore the full and tran log backups to new subscriber db
Create subscriber stored procs in subscriber
Start up distribution agent

I'm looking for opinions on whether it's worth going this route to avoid taking the snapshot.  Data integrity is the number one priority -- if I have to do a snapshot to ensure that, I will do it.

Thanks in advance!

Mike

View Replies View Related

Trans Replication With Updating Subscriber On Sql2000 (single Quote In The Data As Char Data Type)

Hi,

I am trying to setup Trans Replication with updating subscriber on sql2000. One column on few tables got data with single quote (').

How do I handle in this case? Did any one come across such case?

Can I Change default QUOTED IDENTIFIER from ' (single quote) to something else (@@@) on SQL2000?

If yes, how to do?

Thanks
mka

View Replies View Related

MSDN Installation Of SQL2000 Vs. Enterprise SQL2000

We have a 5 gig production DB that is has errors occurring during the log file backup. This is the error: BlkHeader from strip 0 At 2d1f200 ExpectedAt 2d49c00 Size 400 PrevSize 400. It corrupts the log file and our server is running really slow. Does anyone know if it could be that we are using MSDN instead of Enterprise?

View Replies View Related

MSDN SQL2000 To Shrink Wrap SQL2000

Should I uninstall MSDN SQL2000 and then install the shrink wrapped SQL2000, or is there any harm in installing the 'real' SQL2000 over the MSDN version?

View Replies View Related

Sql2000 && Sql2005, Want Localhost To Use Sql2000

 i have sql2000 & sql2005 on the same machine. I am unable to register my localhost in sql2000, get an access denied error. How can I make my localhost use sql2000 database?

View Replies View Related

Deadlocks

Our system is reasonably complex with a lot of non-trivial stored procedures. As the load on our DB increased we're now getting more and more deadlocks (10 per day or so from about a million stored proc executions).

We try to avoid transactions where we can, and we do attempt to optimse stored procs to steer clear of deadlock conditions, but with the sheer number of stored procedures we can't possibly avoid all deadlock conditions.

One solution I'm considering is to re-run stored procs that failed because of a deadlock. In the .net code we'll run the stored proc, check for a deadlock error and if one happened, wait 100ms and try again.

What do you guys think?

View Replies View Related

Deadlocks

Hi EverybodyI am new to sqlserver 2000.I know basics of locks.but i dont know how toresolve deadlock issues.I am cofusing by reading articles with 90%information and remaining 10% missing.Can any one help me which is the goodsite to learn and resolve deadlocks.Note: I create deadlock. when i try to trace deadlock using dbcc traceon(1205,3604,-1).In error log showing nothing about the deadlock.showing created traceon.........Any help would be appreciated.--Message posted via http://www.sqlmonster.com

View Replies View Related

Deadlocks, Why?

We have a problem with a table giving us deadlock issues and we can'tfigure out why.It's a table we write to fairly often perhaps 50 times a minute. Andalso do a select of 200 rows at a time from 4 servers every 5 minutes or so.We are only keeping 48 hours worth of rows in the table which averagesat 30000 a day on a busy day.This table has 1 PK and 2 FKs plus one TEXT column which does notparticipate in the WHERE clause.We are using binded variables.We have applied the latest patch to SQL2003 server running onWindows2003. The patch is supposed to resolve deadlock issues.Anyone have any advice on how to alleviate this problem.Thanks

View Replies View Related

Deadlocks

If an instance of SQL 2005 was in use and was using row versioning,under what circumstances would the below error occur?Transaction (Process ID 56) was deadlocked on lock resources withanother process and has been chosen as the deadlock victim. Rerun thetransactionWe used to get this sort of thing when a large copy process was runningunder a transaction, but all it was doing was reading the records andcreating brand new records yet would still lock the entire table. Oncewe enabled the row versioning, we stopped having this issue, but itseems that there are some circumstances in which it still happens, i.e.the above error.Any ideas how that might occur?

View Replies View Related

Too Many Deadlocks

Hi,

I've got a deadlock problem. The log below has been generated. The problem is that during one day, I have more than 300 deadlocks like it. Before, the were not so many deadlocks.
During past year, the number of users has grow (from 100 before to 500 or 700 now)


*** Deadlock Detected ***
- Requested by: SPID 360 ECID 0 Mode "S"
- Held by: SPID 113 ECID 0 Mode "S"
Index: aaaaa_PK
Table: TABLE_1
Database: MYDB
== Lock: KEY: 22:325576198:1 (ff009ae5078d)
- Requested by: SPID 113 ECID 0 Mode "S"
- Held by: SPID 374 ECID 0 Mode "X"
Index: aaaaa_PK
Table: TABLE_1
Database: MYDB
== Lock: KEY: 22:325576198:1 (ff009ae5078d)
- Requested by: SPID 374 ECID 0 Mode "IX"
- Held by: SPID 360 ECID 0 Mode "S"
Table: TABLE_2
Database: MYDB
== Lock: PAG: 22:1:2428
== Deadlock Lock participant information:
Input Buf: S E L E C T the_rest_of_the_query
SPID: 360 ECID: 0 Statement Type: UNKNOWN TOKEN Line #: 1
Input Buf: s p _ e x e c u t e 8
Input Buf: s p _ c u r s o r 8À B 8 8f ç @ Table I
Input Buf: S E L E C T the_rest_of_the_query
SPID: 360 ECID: 0 Statement Type: SELECT Line #: 1
== Session participant information:
== Deadlock Detected at:
==> Process 360 chosen as deadlock victim


I have done :
- rebuild indexes on all tables (fillfactor 90)
- analysed memory activity

Could a lack of memory be at the origin of the problem ? Which counters in perfmon are significant for memory lack ?

Could the index fill factor could be at the origin of the problem ? At time, it is at 90 percent.


Config : Winnt4 Server, MS-SQL 7 SP4 , 2 GB of RAM , 2 x Xeon 700


Thanks for any help.

View Replies View Related

Deadlocks (I Think)

Hi folks,

I have an application built on top of a questionable DB design which requires overcomplicated selects. The application is experiencing deadlocks regularly, in some cases with only one concurrent user.

I set the trace flag 1204 but am not seeing anything in the Error.log and I initiated a trace in profiler which does not seem to show any deadlock.
Despite having recreated the problem which show my browser hanging indefinitely. When I run the following queries:

SELECT spid, waittime, lastwaittype, waitresource
FROM master..sysprocesses
WHERE waittime > 10000
AND spid > 50

SELECT spid, cmd, status, loginame, open_tran, datediff(s, last_batch, getdate ()) AS [WaitTime(s)]
FROM master..sysprocesses p
WHERE open_tran > 0
AND spid > 50
AND datediff (s, last_batch, getdate ()) > 30
ANd EXISTS (SELECT * FROM master..syslockinfo l
WHERE req_spid = p.spid AND rsc_type <> 2)

I get:

55860978LCK_M_XPAG: 13:1:2573

54AWAITING COMMANDsleeping sa 11499
55UPDATE sleeping sa 21499


respectively. Any help would be welcome.

Thanks in advance,
Don

View Replies View Related

Deadlocks

This is probably a stupid question, but...
Is there any way to totally avoid deadlocks. In some critical applications
we have removed transactions entirely, counting on other means to maintain
database consistency. We still get deadlocks in this area. These are mainly
inserts, and the only thing I can think is that updates to the indexes are
causing multiple page locks which result in deadlocks. Is this true?

Will deadlocks be eliminated in 7.0 with row level locking for this situation?
Or will index page splits still cause a possibility of deadlock contention?

ben

View Replies View Related

Deadlocks

Hi guys,

View Replies View Related

Deadlocks

Hi guys,
Does SQL Server 6.5 log deadlock errors automatically into the errorlog, or do I need to use traceflags ??

TIA
Ju.DBA

View Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved