Replication problems

Hi group
I have the following setup:
A primary sqlserver running windows 2000 server OS
a secondary sqlserver running windows 2003 server OS
Both sqlservers run sqlserver 2000 software, and both logon with the
local administrator account. Both administrator account have the same
password, so accessing \\<servername>\c$\....\repldata shouldnt be a
problem.
the primary sqlserver has been configured as the publication server,
publicating a database called repli_test, as snapshot
The secondary sqlserver has a pull subscription to the repli_test
database.
When I try to pull the database, I get the following error:
The job failed. Unable to determine if the owner
(SQL-BACKUP\Administrator) of job
SQLSERVER-repli_test-repli_test-SQL-BACKUP-repli_test-9DA1AF79-158C-49BD-89B6-64D8F9EF2C21
has server access
(reason: Could not obtain information about Windows NT group/user
'SQL-BACKUP\Administrator'. [SQLSTATE 42000] (Error 8198)).
any suggestions to a solution?
TIA
Kaare
Try changing the job owner to sa.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thank you very much for your reply. It really did the trick.
Unfortunally Im stock on another problem. Replication doesnt seem to
work, if a table contains more than 255 columns. Is there any workaround
on this issue?
TIA
Kaare
|||The main advised workaround is to partition the table and then replicate as
two articles in the same publication. From the point of view of the system,
this could be made transparent as you could have a view which unions the
data from the 2 tables, and call the view the same as the curent table. This
would be taking advantage of non-distributed partitioned views.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication on MSDE2000 and db size problem

Hi,
We have following scenario:
2 PC on WinXP + MSDE2000 + SP4 with production db. Secondary PC works as
failover backup. DBs are connected by merge replication where backup is as
subscriber.
The problem is related to one table with binary column (2K) and its growing
size (over 100MB per day).
sp_spaceused product_map
name rows reserved data index_size unused
Product_map 24238 1056648KB 130448KB 13520KB 912640KB
It seems that on insert rows server allocates more space than need. This
problem occures only when system works on publisher db. It is ok when I
switch it to backup PC.
I have the same systems on W2k + MSDE2000 + SP3a + merge replication and
don't observe the problem like this.
could you help me how to diagnose it more deeply and solve the problem?
Janek
A couple of points 1) are you using text in row?
2) Are you sure the data in this column is the same on the publisher and
subscriber. Depending on how you update your text or image data it may not
be replicated.
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
"Janek" <Janek@.discussions.microsoft.com> wrote in message
news:456DC0D6-FEDC-43BF-8A22-B6CE22069464@.microsoft.com...
> Hi,
> We have following scenario:
> 2 PC on WinXP + MSDE2000 + SP4 with production db. Secondary PC works as
> failover backup. DBs are connected by merge replication where backup is as
> subscriber.
> The problem is related to one table with binary column (2K) and its
> growing
> size (over 100MB per day).
> sp_spaceused product_map
> name rows reserved data index_size
> unused
> Product_map 24238 1056648KB 130448KB 13520KB 912640KB
> It seems that on insert rows server allocates more space than need. This
> problem occures only when system works on publisher db. It is ok when I
> switch it to backup PC.
> I have the same systems on W2k + MSDE2000 + SP3a + merge replication and
> don't observe the problem like this.
> could you help me how to diagnose it more deeply and solve the problem?
> Janek
|||1) data type for table is: int, smallint, int, char(11), smallint, smallint,
binary(2001), bit, datetime, int
2) All data is replicating, I can see it on reports on each machines. From
sp_spaceused report I see almost 1GB of unused space.
I know only one workaround:
dbcc dbreindex (.... + shrink db - a few cycles makes db to similar
backup db size.
At the moment system is working on backup PC without problem and new data is
refreshed to publisher.
Janek
"Hilary Cotter" wrote:

> A couple of points 1) are you using text in row?
> 2) Are you sure the data in this column is the same on the publisher and
> subscriber. Depending on how you update your text or image data it may not
> be replicated.
> --
> 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
>
> "Janek" <Janek@.discussions.microsoft.com> wrote in message
> news:456DC0D6-FEDC-43BF-8A22-B6CE22069464@.microsoft.com...
>
>

Replication in 2005

We need to push all the changes across network to a secondary, reporting
server, on a timely manner. We were using replication in SQL200, but it
takes a lot server resources. Any new feathers in SQL2005?
There are a lot of new features in SQL 2005. Transactional replication will
place fewer locks on the publisher by default during snapshot generation.
You could also look at database snapshots or log shipping for this.
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
"awan" <awan@.discussions.microsoft.com> wrote in message
news:5D8A9D21-2AF4-4EB7-AAFA-603FCDA399FA@.microsoft.com...
> We need to push all the changes across network to a secondary, reporting
> server, on a timely manner. We were using replication in SQL200, but it
> takes a lot server resources. Any new feathers in SQL2005?