Sql2000 Replication
Jul 23, 2005hello,
also wanted to confirm which versions of sql2000 can do replication.
Would be nice to have fault-tolerance via replication so as to have a
hot-standby.
Oskar
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 a
hot-standby.
Oskar
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
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
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
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
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?
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?
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.
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
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
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
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 1 Replies View Related
i am in the process of Migrating SQL 2000 to my new SQL2000 server i want to know the what would the best way for me to migrate one SQL server to another SQL server on the same network and rename the new server to the old server and bring it up for use in our ecommerce website.
Hi,I have made a web application using SQL Server 2005
Express with a few admin pages that require login. I used the SQL
Server Managment Studio Express to setup users and groups and it works
fine. But the web server has SQL Server 2000 and all I get is a
user id and password to access the database. It seems I cannot use the
Login control I put on my "login.aspx" page becuase it uses the
integrated authentication which chokes on 2000. I am afraid I wonlt be
able to use some of the 2.0 features such as profiles, ... Is
this the way 2.0 works with SQL Server 2000? Should I ditch the ISP if
they only give me a single access to database with no provisions to
create users. (I was told I had to create a "Users" table and manually
assign ids and passwords and that I can only use the user id and
password they supplied to setup the connection string in the script.)I appreciate your help.
Does anyone know when SP1 will be available for SQL2000??
Thanks,
Steve Bajada
Are there any advantages/disadvantages of running SQL2K on NT4 as opposed to running on WIN2K?
View 1 Replies View Relatedpls tell me abt log shipping in sql2000
I'm getting this, after upgrading from 2000 to 2005.Replication-Replication Distribution Subsystem: agent (null) failed.The subscription to publication '(null)' has expired or does notexist.The only suggestions I've seen are to dump all subscriptions. Sincewe have several dozen publications to several servers, is there adecent way to script it all out, if that's the only suggestion?Thanks in advance.
View 3 Replies View RelatedHi,I have transactional replication set up on on of our MS SQL 2000 (SP4)Std Edition database serverBecause of an unfortunate scenario, I had to restore one of thepublication databases. I scripted the replication module and droppedthe publication first. Then did a full restore.When I try to set up the replication thru the script, it created thepublication with the following error messageServer: Msg 2714, Level 16, State 5, Procedure SYNC_FCR ToGPRPTS_GL00100, Line 1There is already an object named 'SYNC_FCR To GPRPTS_GL00100' in thedatabase.It seems the previous replication has set up these system viewsSYNC_FCR To GPRPTS_GL00100. And I have tried dropping the replicationmodule again to see if it drops the views but it didn't.The replication fails with some wired error & complains about thisviews when I try to run the synch..I even tried running the sp_removedbreplication to drop thereplication module, but the views do not seem to disappear.My question is how do I remove these system views or how do I make thereplication work without using these views or create new views.. Whyis this creating those system views in the first place?I would appreciate if anyone can help me fix this issue. Please feelfree to let me know if any additional information or scripts needed.Thanks in advance..Regards,Aravin Rajendra.
View 2 Replies View RelatedI am developing a Crystal Reports App in VS2005 (VB). I was originally working on an XP machine with MSDE and stored procedures where it worked fine.
I then transferred the development to a Win2003 machine with SQL2000 and am now getting the following error;
Failed to open a rowset. Description: 'Get_Calls_By_MLO_Date' expects parameter '@DT1' which was not supplied. Plus some other error detail.
Here is the SP.
CREATE PROCEDURE Get_Calls_By_MLO_By_Date @DT1 datetime, @DT2 datetimeASSELECT MLO, CallNo, DT, Type FROM ActionsWHERE dt >= @DT1 AND dt <= @DT2 AND ActionID=1 ORDER BY MLO, DTGO
If I transfer everything back to the XP machine it works fine.
Any ideas?
Thanks
Terry.
How to lock a Row in SQL2000 so that nobody can select that row.
I applied ROWLOCK, but i am not finding the way.
My query is "SELECT * FROM tablename WITH (ROWLOCK)"
Is this the correct way to write locks.
I would be thankful if u help me
I am exporting data to an Excel file via a scheduled DTS package. I need to be able to either overwrite the existing Excel file or delete it. I haven't found a way to do this yet. Any help, comments, or direction will be appreciated. TIA
Paul
I want to insert some data into my SQLServer,For example:insert into xcjl(zch,xcsj) values('027741',getdate())
but ,the "zch" maybe have a few data,I want to insert these step by step,how can I do?
Hi all,
We're beginning to migrate our 6.5 DB's to SQL2000. A question came up regarding naming conventions for stored procedures. In BOL it says that for SQL2000:
"Stored procedures with the prefix sp_ are first looked up in master. If a user-defined stored procedure has the same name as a system-supplied stored procedure residing in master, SQL Server always finds the system-supplied stored procedure. "
Behavior in 6.5 was the opposite: SQL Server searched the current database followed by a search in master.
We started several months ago renaming user stored procedures to "usp_XXX", but we still have many non-system sp's that still use "sp_". I'm looking for opinions of whether we should bite the bullet now and rename all our non-system sp's at this time; prior to moving our production environment to SQL2000. Will we see a performance gain since SQL will not have to hit master first before going to the current DB?
Any and all opinions welcome!
Thanks,
Tom Rosebrook
EMJ
When bcp'ing in data into an sql 6.5 table that is NOT nullable, records in the text file that contain nulls are ommited, but valid records without nulls are inserted.
However, using exactly the same table structure and files on a newly installed sql 2000 server (sp2), as soon as the first invalid record in the text file (i.e. with a null value)is encountered, bcp'ing is terminated and NO records are inserted.
I can't find any option in bcp/sql 2000 to allow me to carry out a load as before.
The help files state that the default no. of invalid records allowed is 10 (both versions sql), and explicitly setting the -m option of bcp to 10 still doesn't work.
Most of the data i receive has at least one duff record
Is there an option in sql 2000 that allows me to have x number of duff records inserted before a full rollsback occurs?
I can't find anything in technet, msdn or books online.
In a replication environment:
Does SQL 2000 standard edition support replication if it would be configured as a subscriber.
Is SQL 2000 Enterprise Edition required for a Publisher and Distributor or can you get away with standard edition.
In a web site environment how many CALs are needed when users access the database via webservers and middleware.
Thanks
I am experimenting with the FOR XML AUTO clause in SQL2000, but instead of nicely structured XML I get one continuous string oftags that can't be parsed by IE5.5
The BOL seem to indicate just running the query in Query Analyser will produce nicely formatted XML output - can anybody tell me what is wrong?
I need some strong points for the management to convince them to upgrade to sql2000 now than waiting for 6 months.
We are currently in process of developing this new product. All development is on sql7. I want to upgrade our database to sql2000 now rather than waiting after the release which might be in another 3 months.
I crashed my HP portable that has SQL2000 ENT installed and I re-installed XP-Pro +SP1 and when I install SQL2000 ENT it refused to install saying ENT cannot install in this O/S. Did I miss anything ?
I went and checked another XP-Pro W/S and SQL2000 is intalled OK.
Anybody has any idea ?
Thanks,
Frank
Does a script that run with sql7 automatically run with sql2000?
I would like to know if my script will run if I change version.
Is it possible to fire a update trigger from SQL6.5 table to update a SQL2000 server database table field value? (upgrade this 'legacy' to sql2k now is not an option)
If it is not possible, is there a way to accomplish it?
thanks
David
I am trying to give developers access to use profiler without giving them sysadmin fixed role is this possible ???
View 3 Replies View RelatedHi,
I noticed that when I installed SQL2000,with "typical install",
the default, the following will be used:
SQL collation (dictionary order, case-insensitive, assent sensitive)
sp_helpsort will give
SQL_Latin1_General_CP1_CI_AI
Is there any difference if I choose the "custom install", then and choose
the windows locale which gives the result of sp_helpsort:
Latin1_General_CI_AI
SQL_Latin1_General_CP1_CI_AI is supposed for backward compatibilty, so are
they actually equivalent ??
Any impact or difference we have to be aware of ??
Anyone knows..Thx