Pushing Data to Another SQL Server

Hi,
I have a production SQL2000 in Location A with Database A. I have another SQL2000 in Location B. I want to copy Database A to Location B. Any changes in Database A in Location A gets pushed to Location B.
Can I do this in 2000? TIAyes you can|||yes you can

Are you sure?

:D|||Are you sure?

:D

Absolutely ... the method of last resort would be sneakernet ... but I would try other M$oft methods built into SQL Server first.

Unless he meant seven years ago ... then I would have to say probably not.

:psql

push subscribe problem(String data, right truncation)

os : windows2000 server
sql : sql2000 enterprise edition
mdac version is same each other.. version 2.8
i have two sql server(devsrv and parkchangsoon)
i configured the transaction replication
parkchangsoon : publisher,distributer
devsrv : subscriber
articles are 10 of all tables and 10 of all procedures
at first
the snapshot agent status is succss and the last action is "the snapshot of
24 articles have created"
after that
the distributer agent is pushing to devsrv (subscriber system)
but the distributer agent status is fail and the last action is "could not
bulk copy to 'jobs' table"
so..
i saw the distributer agent error information
publisher(P) : parkchangsoon agent(A) : PARKCHANGSOON-albaroot_3th-DEVSRV-5
publish(U) : albaroot_3th subscribe : DEVSRV:albaroot_3th
error message(E) : could not bulk copy to 'jobs' table
last command (V) : select * from workey_jobs where 1=1
error infomation(E) : String data, right truncation
source : DEVSRV(ODBC); eror number : 22001
below is the schema of the jobs table
CREATE TABLE [devuser].[Jobs] (
[seq] [int] IDENTITY (1, 1) NOT NULL ,
[title] [varchar] (100) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[findPrsn] [tinyint] NOT NULL ,
[ageZn] [varchar] (50) COLLATE Korean_Wansung_CI_AS NULL ,
[applyRght] [varchar] (4000) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[emplrId] [varchar] (30) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[readCnt] [int] NOT NULL ,
[sido] [tinyint] NOT NULL ,
[workTyp] [char] (8) COLLATE Korean_Wansung_CI_AS NULL ,
[applyDcmnt] [varchar] (100) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[findYmd2] [smalldatetime] NOT NULL ,
[gugun] [tinyint] NOT NULL ,
[finishYmd] [bit] NOT NULL ,
[ymd] [smalldatetime] NOT NULL ,
[particular] [char] (1) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[position] [varchar] (100) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[makeup_color] [bit] NOT NULL ,
[makeup_icon] [bit] NOT NULL ,
[makeup_marquee] [bit] NOT NULL ,
[logo] [varchar] (50) COLLATE Korean_Wansung_CI_AS NOT NULL ,
[endymd] [smalldatetime] NOT NULL ,
[jobtype1] [tinyint] NULL ,
[jobtype2] [tinyint] NULL ,
[jobtype3] [tinyint] NULL ,
[paytype] [char] (4) COLLATE Korean_Wansung_CI_AS NULL ,
[pay1] [int] NULL ,
[pay2] [bit] NULL ,
[suprise] [tinyint] NULL ,
[ts] [timestamp] NULL ,
[visible] [bit] NULL ,
[createdYmd] [smalldatetime] NULL ,
[msrepl_tran_version] [uniqueidentifier] NOT NULL
) ON [PRIMARY]
GO
nonclustered primary key is seq column
how can i solve this problem?
any suggestion?
help...
thanks
On each article can you ensure that the collation is sent over - this is a
checkbox option on the article properties, snapshot tab.
Regards,
Paul Ibison
|||thanks for replying.~
on the article properties, snapshot tab..
those three options are checked..
Includes declared referential integrity
clustered index
non clustered index
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:us917DwbEHA.2760@.TK2MSFTNGP09.phx.gbl...
> On each article can you ensure that the collation is sent over - this is a
> checkbox option on the article properties, snapshot tab.
> Regards,
> Paul Ibison
>
|||OK - select the collation checkbox for each table and
reinitialize - hopefully this will remove the truncation
issue which may be due to different codepages.
Regards,
Paul Ibison

Publisher is empty under Replication Monitor - Publisher.! But replication is still runnin

I have a wired situation..!
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..
You could try running sp_MSload_replication_status.
To investigate further I'd like to know if you see the publication under the
"Replication" folder and/or the "Publications" folder in the published
database.
Also, there was an issue with this prior to sp4
(http://support.microsoft.com/kb/814032) so please ensure that you've got
the latest sp.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I still have this issue.. Any thoughts? ... ideas.. ?
Thanks in advance..
Query Builder wrote:[vbcol=seagreen]
> Yes, I do see the publications under the Replication --> Publication
> tab. I can also confirm that the replication is working as it is
> pushing those updates to the subscriber. I am unable to run the
> sp_MSload_replication_status as it is returning the following error..
> Server: Msg 8152, Level 16, State 6, Procedure
> sp_MSload_replication_status, Line 19
> String or binary data would be truncated.
> The statement has been terminated.
> Thanks for the update. I would appreciate if you can help me figure out
> the issue...
> Thanks again..
>
> On Nov 3, 4:42 am, "Paul Ibison" <Paul.Ibi...@.Pygmalion.Com> wrote:
|||I had finally figured out the issue... I changed the SQL Jobs
associated with the replication and when i changed back the sql job
names it appeared under my Replication monitor group window...
Query Builder wrote:[vbcol=seagreen]
> I still have this issue.. Any thoughts? ... ideas.. ?
> Thanks in advance..
>
> Query Builder wrote:

Publisher is empty under Replication Monitor - Publisher.! But replication is still runnin

I have a wired situation..!

I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).

It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.

I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...

After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...

All it says is (No Items)...

I would appreciate any help to correct this issue... Thanks in advance..Has anyone seen this issue? Any thoughts? Thanks in advance..

Query Builder wrote:

Quote:

Originally Posted by

I have a wired situation..!
>
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
>
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
>
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
>
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
>
All it says is (No Items)...
>
I would appreciate any help to correct this issue... Thanks in advance..

|||I finally found the solution. The problem started when I renamed the
sql jobs related to the replication. When I changed the name back to
what it was, and now I can see the replication tree under the
replication Monitor window...

Query Builder wrote:

Quote:

Originally Posted by

Has anyone seen this issue? Any thoughts? Thanks in advance..
>
>
Query Builder wrote:

Quote:

Originally Posted by

I have a wired situation..!

I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).

It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.

I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...

After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...

All it says is (No Items)...

I would appreciate any help to correct this issue... Thanks in advance..

Publication has expired

I have setup transaction replication using seperate server for distribution
box.
Server A - Publisher (Win2003, SQL2000 SP818)
Server B - Distributor (Win2003, SQL2000 SP818)
Server C - Subscriber1 (Win2003 and SQL2000 SP818)
Server D - Subscriber2 (Win2003 and SQL2000 SP818)
Server E - Subscriber3 (Win2000, SQL2000 SP818)
Server A has 3 publishers and each publisher has more than 10 articles, one
of them we use it for monitoring replication by update a datetime column from
sql job.
The trans. replication are running fine execpt the subscriber3. This
subsciber always get sthe subscription expires errors, but the monitor
article does get updated. And the wired thing is the replication monitor on
the distribution server shows that the agent is in suspect and no reponse
within 10 min after each snapshot/initation.
I did query the MSDistribution_History and there is only one row which the
date I ran the snspshot. All the retention and history period are default.
Does anyone knows that it is Win2003 to Win2000 issue or something else.
Thanks in advance
This guy expired prematurely because your history retention is less than
your publication retention. Bump this setting up to your publication
retention, and be highly proactive about sensing when this guy has dropped
off the network for more than 1 day.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"kc" <kc@.discussions.microsoft.com> wrote in message
news:7B0A51D7-F9BD-4281-A7F3-E8144164F02A@.microsoft.com...
> I have setup transaction replication using seperate server for
distribution
> box.
> Server A - Publisher (Win2003, SQL2000 SP818)
> Server B - Distributor (Win2003, SQL2000 SP818)
> Server C - Subscriber1 (Win2003 and SQL2000 SP818)
> Server D - Subscriber2 (Win2003 and SQL2000 SP818)
> Server E - Subscriber3 (Win2000, SQL2000 SP818)
> Server A has 3 publishers and each publisher has more than 10 articles,
one
> of them we use it for monitoring replication by update a datetime column
from
> sql job.
> The trans. replication are running fine execpt the subscriber3. This
> subsciber always get sthe subscription expires errors, but the monitor
> article does get updated. And the wired thing is the replication monitor
on
> the distribution server shows that the agent is in suspect and no reponse
> within 10 min after each snapshot/initation.
> I did query the MSDistribution_History and there is only one row which the
> date I ran the snspshot. All the retention and history period are
default.
> Does anyone knows that it is Win2003 to Win2000 issue or something else.
> Thanks in advance
|||In my case, the monitor article in the subscriber had same time as the
publisher when it was mark for expiration. Therefore it is not a network
issue.
By default, the hsitory rentention is 48 hrs and transaction rentention is
72 hrs, so I don't understand what do you mean that I need to bump the
setting up?
Thanks
KC
"Hilary Cotter" wrote:

> This guy expired prematurely because your history retention is less than
> your publication retention. Bump this setting up to your publication
> retention, and be highly proactive about sensing when this guy has dropped
> off the network for more than 1 day.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "kc" <kc@.discussions.microsoft.com> wrote in message
> news:7B0A51D7-F9BD-4281-A7F3-E8144164F02A@.microsoft.com...
> distribution
> one
> from
> on
> default.
>
>