Replication error

Hi

I am trying to replicate a database using the snapshot method. The publication worked fine, when the second server tried to pull the replication, it started, but then come up with the following error whilst creating the tables.

Insert Error: Column name or number of supplied values does not match table definition.

Any ideas?

cheers

SimonThe error usually occurs in transactional replication when someone accidentally changed the DDL in subscriber. You can reinitialize the subscription from the publication database and refresh your subscription.|||still no luck. Didn't help. Stil had the same error, any other ideas?

cheers

Replication Conflict Auto Notification (How)

Hi

I'm Running SQL 2k - Mainly Merge Replication.

Can Someone point me in the right direction on how best to Alert myself/Operator via email when a conflict occurs.

I use xp_sendmail regularly so can deal with that part

I've tried looking for a solution but with no success.

Having to keep opening the Conflict Viewer to check is becomming a Bit Tiresome.

The Only way I can think of is running a batch Job to look at the rowcount of conflict tables (Possibly using a cursor and dynamically built Select Count(*) statements from sysobjects to get conflict table names).

or

If Conflicts are flagged in the system Replication tables query them but I don't know which table if any exist.

Theres gotta be an easier way - I must be missing something

Any Help Greatly appreciated

thx

GWCheck Lumigent (http://www.lumigent.com) website for latest tool on notification and its free.|||Cool

thx again Satya

GW

Replication Breaks after applying SP4

Hi
I installed SP4 on our enterprise server this morning and now all
replication jobs fail with the message "No such interface supported"
Has anyone seen this before / know how to resolve this?
We run Enterprise Edition on Win2003
Many Thanks
D
nope. I suggest you re-register the replication dll's and exes. I think you
can find them in c:\program files\microsoft sql server\mssql\80\com
"DJ" <DJ@.discussions.microsoft.com> wrote in message
news:CA106D94-FD82-4099-A342-BF75A0910D5B@.microsoft.com...
> Hi
> I installed SP4 on our enterprise server this morning and now all
> replication jobs fail with the message "No such interface supported"
> Has anyone seen this before / know how to resolve this?
> We run Enterprise Edition on Win2003
> Many Thanks
> D
|||There was apparently an as yet not fully explained registry ACLing problem in
SP4 setup per the following thread (reported by Tomasz Skorupa originally):
http://groups.google.com/group/micro...85 a5a37097d4
With more than one person hitting the same problem, I would like to try
again and see if I can find out more about the cause of it. Was the user
running SP4 setup on the machine the same as the one running SQL Server Agent
service? If not, did the account running SP4 have privilege for enumerating
account information for the SQL Server Agent service account?
-Raymond Mak
"DJ" wrote:

> Hi
> I installed SP4 on our enterprise server this morning and now all
> replication jobs fail with the message "No such interface supported"
> Has anyone seen this before / know how to resolve this?
> We run Enterprise Edition on Win2003
> Many Thanks
> D
|||Thanks for the reply Raymond and apologies for not replying sooner but I have
been off work.
I tried re-registering the dll following the steps you mentioned in the
other thread but this did not work for me.
I re-registered them and stopped and started SQL Agent. Did I need to do
anything else?
The version of sqlrepss.dll on my instance is :2000.80.2039.0
I was not connected as the service account so I may not have had the
prvilages for enumeration the account informaion.
I can run the replication from the command line but I always get the error
when using Enterprise Manager.
Do you have any other suggestions to resolve this?
Many Thanks
Daryl
"Raymond Mak [MSFT]" wrote:
[vbcol=seagreen]
> There was apparently an as yet not fully explained registry ACLing problem in
> SP4 setup per the following thread (reported by Tomasz Skorupa originally):
> http://groups.google.com/group/micro...85 a5a37097d4
> With more than one person hitting the same problem, I would like to try
> again and see if I can find out more about the cause of it. Was the user
> running SP4 setup on the machine the same as the one running SQL Server Agent
> service? If not, did the account running SP4 have privilege for enumerating
> account information for the SQL Server Agent service account?
> -Raymond Mak
>
> "DJ" wrote:
sql

Replication and Reports

Hi!
I have transactional replication setup to a remote server. My
application is pointing to that server for reporting function.
Everytime I ran a report it locks the replication and replication
times out. In my reports I specified No Lock (not sure if this did
anything) but reporting still locking replication.
Any suggestions on how to implement reporting and replication so the
latter doesn't lock the former?
Thank you,
T.
In your reports, perhaps you have missed some nolock hints. It's easier to
set the transaction isolation level to read_uncommitted for the reporting
connection. Once that is done, start the distribution agent and if there is
still a problem, run profiler for the blocked process report (assuming sql
server 2005).
Also, if you are on sql server 2005, you might also want to investigate the
read_committed_snapshot option instead of nolock.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||On Feb 21, 10:13 am, "tolcis" <nytolly...@.gmail.com> wrote:
> Hi!
> I have transactional replication setup to a remote server. My
> application is pointing to that server for reporting function.
> Everytime I ran a report it locks the replication and replication
> times out. In my reports I specified No Lock (not sure if this did
> anything) but reporting still locking replication.
> Any suggestions on how to implement reporting and replication so the
> latter doesn't lock the former?
> Thank you,
> T.
Start by reviewing the indexes that are on your tables, and the
execution plans of the queries that your reports are running.
Reporting functions usually require a totally different indexing
strategy than transactional processing does. Proper indexes and
efficient queries will help minimize locking.

Replication and Reports

Hi!
I have transactional replication setup to a remote server. My
application is pointing to that server for reporting function.
Everytime I ran a report it locks the replication and replication
times out. In my reports I specified No Lock (not sure if this did
anything) but reporting still locking replication.
Any suggestions on how to implement reporting and replication so the
latter doesn't lock the former?
Thank you,
T.In your reports, perhaps you have missed some nolock hints. It's easier to
set the transaction isolation level to read_uncommitted for the reporting
connection. Once that is done, start the distribution agent and if there is
still a problem, run profiler for the blocked process report (assuming sql
server 2005).
Also, if you are on sql server 2005, you might also want to investigate the
read_committed_snapshot option instead of nolock.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||On Feb 21, 10:13 am, "tolcis" <nytolly...@.gmail.com> wrote:
> Hi!
> I have transactional replication setup to a remote server. My
> application is pointing to that server for reporting function.
> Everytime I ran a report it locks the replication and replication
> times out. In my reports I specified No Lock (not sure if this did
> anything) but reporting still locking replication.
> Any suggestions on how to implement reporting and replication so the
> latter doesn't lock the former?
> Thank you,
> T.
Start by reviewing the indexes that are on your tables, and the
execution plans of the queries that your reports are running.
Reporting functions usually require a totally different indexing
strategy than transactional processing does. Proper indexes and
efficient queries will help minimize locking.

Replication and Enterprise Manager

Hi
I have a very interesting situation with my replication. Replication works
great if I leave opened Enterprise Manager, but when I close it,
replication and SQL server does not work any more.
If I made a "mistake" and close EM, that the next morning SQL server does
not respond even if I reboot server. I must reinstall SQL service pack and
than it works. This was happened 5 time and now I am positivly shure that
this is the problem.
And yes ... this is SQL 2000 with SP3, Windows 2000 Server with Terminal
services installed.
Did anyone knows about this funny problem?
Thank you
what security context are your replication jobs running under? It sounds
like they are not running under a system administrator account.
To fix this right click on your agents and look at your agent properties.
Change the owner account to an account which is in the system administrator
role.
<dklancar@.nkbm.si> wrote in message
news:uxK3yvvFEHA.3188@.TK2MSFTNGP10.phx.gbl...
> Hi
> I have a very interesting situation with my replication. Replication works
> great if I leave opened Enterprise Manager, but when I close it,
> replication and SQL server does not work any more.
> If I made a "mistake" and close EM, that the next morning SQL server does
> not respond even if I reboot server. I must reinstall SQL service pack and
> than it works. This was happened 5 time and now I am positivly shure that
> this is the problem.
> And yes ... this is SQL 2000 with SP3, Windows 2000 Server with Terminal
> services installed.
> Did anyone knows about this funny problem?
> Thank you
|||Thank you for response, but I must tell you, that all agent are running as
user listed in the system admin role.
Thank you again.
|||If SQL Server won't start, is there anything listed in hte Windows Application Log or the SQL Server log that sheds any light?
Regards,
Paul Ibison

Replication

Hi!

I'm trying to implement a transactional replication
with SQL Server 2000. I'm new on this issue. ;)

I tried to configure the distribution, but i received a message, that i didn't understand and that i send you in attachment.

Could you, please, tellme what does it means? And what should be done?

Thank's in advanced

My best regards

siffAs the message says, you must change the SQL Server Agent account (service). Use a domain account that gives you access to the replication folders.
The Snapshot Agent must be able to connect to the publication database on the Publisher and the distribution database on the Distributor. By default on Windows 2000, the snapshot folder used for replication is located at C:\Program Files\Microsoft SQL Server\Mssql\Repldata on the distributor. Each Snapshot Agent must have full control access to this folder. By default on W2000, the replication agents run in the security context of SQL Server Agent domain user account. If the domain user account is not member of the local Administrators group on the Distributor, you should create a shere for the snapshot folder and grant necessary permissions to the share to the domain account under which these replication agents run.

Originally posted by siff
Hi!

I'm trying to implement a transactional replication
with SQL Server 2000. I'm new on this issue. ;)

I tried to configure the distribution, but i received a message, that i didn't understand and that i send you in attachment.

Could you, please, tellme what does it means? And what should be done?

Thank's in advanced

My best regards

siff|||Can u give more details on server roles. Servers involved and their roles (Publisher, Distributor and Subscriber). Are they part of domain / work group etc.

If the servers are part of same domain, add a domain account to the local admin group of server and use that account to run the Sql server agent

If the servers are part of work group then u need to create trusted user connection between the servers.

Replication

Hi
I have setup transaction replication, I defined publisher. Now I have new
server
Where I run create script for database and table from publisher server.
First time on my subscriber server's table has rows, I can’t restore from
backup because of time (it took about 8 hrs. to restore).
After setting up replication, my new subscriber got no rows, how tried
tranactional,snapshot replication data is populated on subscriber.
Advice me how to proceed with restoring db on my subscriber m/c.
Thanks
Kalyan
Advice me how to proceed without restoring db on my subscriber m/c.
"Kalyan" wrote:

> Hi
> I have setup transaction replication, I defined publisher. Now I have new
> server
> Where I run create script for database and table from publisher server.
> First time on my subscriber server's table has rows, I can’t restore from
> backup because of time (it took about 8 hrs. to restore).
> After setting up replication, my new subscriber got no rows, how tried
> tranactional,snapshot replication data is populated on subscriber.
>
> Advice me how to proceed with restoring db on my subscriber m/c.
> Thanks
> Kalyan
>

Replication

Hi
I have one replication database and I need to move this database another
disk, but I dont wan't to remove the replication, my question is
How I can to move this database without remove the replication?"Valero" <Valero@.discussions.microsoft.com> wrote in message
news:D1B0C9DB-EBF3-41AE-8914-A5A45F37C5AC@.microsoft.com...
> Hi
> I have one replication database and I need to move this database another
> disk, but I dont wan't to remove the replication, my question is
> How I can to move this database without remove the replication?
>
Are you talking subscriber or publisher?
If you're talking subscriber, I believe you can sp_detachdb and sp_attachdb
(it's been awhile since I've had to do this.)
If you're talking the publisher, that's trickier.
What I've done is stop SQL Server, move the files, start sql server, ignore
the errors, and update the appropriate rows in the master DB, and then
restart SQL Server.

>

Replicating Stored Procedure

Hi:
I made a change to the stored proc in the publisher database but the change
did not get replicated. I should not have to run the snapshot agent again to
do that. Please let me know how can this be easily done.
Thanks
Mike,
this is better handled in SQL 2005, but in 2000 we can use sp_addscriptexec,
linked servers or manual addition of the new code. For this reason I
generally add the code parts of my publications (sps, views, functions) to a
separate publication, so if I decide to use replication to send them over, it
doesn't disturb my main publication.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Use sp_addscriptexec to send the commands if your subscribers were deployed
through UNC(file copies). If there were deployed through ftp you will have
to connect to them individual and run the commands individually.
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
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:15028C08-3FA7-4647-9C23-7A2698AF8C41@.microsoft.com...
> Hi:
> I made a change to the stored proc in the publisher database but the
> change
> did not get replicated. I should not have to run the snapshot agent again
> to
> do that. Please let me know how can this be easily done.
> Thanks
>