REPLICATION ERROR

hi,
I am dealing with merge replication between a remote server and local
since last 2 months
From last 15 days, replication stops frequently and showing the
error message
The process could not enumerate the changes at the 'subscriber'
Can I know the reason for this?
Thanks
Soura
this is a normal message. Restart your agent and 95% or more of the time
this message will clear.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:EE708A73-322F-4D7B-8AF0-47E2AD65EC80@.microsoft.com...
> hi,
> I am dealing with merge replication between a remote server and local
> since last 2 months
> From last 15 days, replication stops frequently and showing the
> error message
> The process could not enumerate the changes at the 'subscriber'
> Can I know the reason for this?
> Thanks
> Soura
|||hi Hilary,
Yes, once I give 'start synchronizing' then it starts to work normally.
Now, my question is
why is this happening?
what is the permanent solution for this?
Thanks,
soura
"Hilary Cotter" wrote:

> this is a normal message. Restart your agent and 95% or more of the time
> this message will clear.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
> "SouRa" <SouRa@.discussions.microsoft.com> wrote in message
> news:EE708A73-322F-4D7B-8AF0-47E2AD65EC80@.microsoft.com...
>
>

REPLICATION ERROR

Hi,
I am dealing with merge replication between local & remote servers.
Last week the following error occurs two times.
The merge process could not perform retention-based meta data cleanup in
database 'TEST'.
(Source: Merge Replication Provider (Agent); Error number: -2147199467)
The merge process timed out while executing a query. Reconfigure the
QueryTimeout parameter and retry the operation.
(Source: TSERVER (Data source); Error number: 0)
First I gave 'start synchronizing' after that I restarted the merge agent
but no use .
Finally after restarting the server(publisher), it came to end. Now its
working fine.
My question is,
1. what is the reason for this error?
2. Is this a Symptom for future problems (ie., like database corruption)
but when I run CHECKDB command, no error has been shown. It says the DB
is fine.
Can any one advice me?
Thanks,
Soura.
This error is basically a timeout and can happen for many reasons. They
are usually assoicated with slow servers or subscribers but could also
be network problems. Reindexing your tables, especially
msmerge_contents, msmerge_Genhistory, msmerge_tombstone can help if you
have a lot of replication metadata. If you have a large amount of
metadata in those tables you can also run sp_mergecleanupmetadata. This
will cause you to generate and apply a new snapshot however. If you
choose to use the sp_mergecleanupmeta data and have a large number or
rows in your merge tables. You might want to truncate the
msmerge_contents and maybe the msmerge_genhistory table at the
publisher and subcribers before running as it will also get a timeout
doing the cleanup.
|||Hi Sounder,
I found this from One article.
In case of this error
stop the merge agent and do a dbcc dbreindex -- to all tables by using that
reindex procedure.
Thanks.
Herbert
"SouRa" wrote:

> Hi,
> I am dealing with merge replication between local & remote servers.
> Last week the following error occurs two times.
> The merge process could not perform retention-based meta data cleanup in
> database 'TEST'.
> (Source: Merge Replication Provider (Agent); Error number: -2147199467)
> ----
> --
> The merge process timed out while executing a query. Reconfigure the
> QueryTimeout parameter and retry the operation.
> (Source: TSERVER (Data source); Error number: 0)
> First I gave 'start synchronizing' after that I restarted the merge agent
> but no use .
> Finally after restarting the server(publisher), it came to end. Now its
> working fine.
> My question is,
> 1. what is the reason for this error?
> 2. Is this a Symptom for future problems (ie., like database corruption)
> but when I run CHECKDB command, no error has been shown. It says the DB
> is fine.
> Can any one advice me?
> Thanks,
> Soura.
|||Hi Sounder,
I find this from one article.
In case of these kind of error
stop the merge agent and do a dbcc dbreindex -- Do reindex to all tables
using that procedure
Thanks
Herbert
"SouRa" wrote:

> Hi,
> I am dealing with merge replication between local & remote servers.
> Last week the following error occurs two times.
> The merge process could not perform retention-based meta data cleanup in
> database 'TEST'.
> (Source: Merge Replication Provider (Agent); Error number: -2147199467)
> ----
> --
> The merge process timed out while executing a query. Reconfigure the
> QueryTimeout parameter and retry the operation.
> (Source: TSERVER (Data source); Error number: 0)
> First I gave 'start synchronizing' after that I restarted the merge agent
> but no use .
> Finally after restarting the server(publisher), it came to end. Now its
> working fine.
> My question is,
> 1. what is the reason for this error?
> 2. Is this a Symptom for future problems (ie., like database corruption)
> but when I run CHECKDB command, no error has been shown. It says the DB
> is fine.
> Can any one advice me?
> Thanks,
> Soura.

Replication Dilemma - Need a Solution/Ideas

Hi all,
Here's a situation I have been challenged with....
I will have up to 6 remote databases and I want them all to update a
single master database in a company with multiple production plants.
The remote databases will just have active work in a plant and only the
work that is in that particular plant. I would like the master
database to have all information from the plants. Ideally, the remote
plants will update the master database once an hour (consisting of new
inserts of orders coming into the plant and updated records as work
moves through the plant). Once work ships from a plant, I want to purge
it off the remote plant database, yet keep it on the master.
It seems with replication, if I delete records at a plant, it will
delete on the master, which is not what I want. The master is
basically the database customer service will use and needs active
status on work in the plants and would contain a couple of years of
information. The remote plant databases have just the data they need
and our optimized. A remote database has 20 tables, with multiple
tables with 1 to 20 million records actively inserted/udated each day.
The schema of the master is identical to the plants and all keys at
each plant are guaranteed unique.
Any ideas would be greatly appreciated, as I am currently contemplating
using bcp in an automated fashion and anticipating a nightmare of
keeping referential integrity.
Regards
What I think you need to do is the following.
1) create a filter on your publications which filter by plant id. Hopefully
you have a column to do this with. Then when you create you publication and
get to the specify articles dialog click on the browse button to the right
of your tables. Select the snapshot tab, and select the option to delete the
data which matches the row filter.
2) In the table article properties dialog, click on the commands tab and
replace the delete command with the word NONE - this will prevent deletes
from being 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
<davidkrainess@.yahoo.com> wrote in message
news:1131135473.722037.278030@.g44g2000cwa.googlegr oups.com...
> Hi all,
> Here's a situation I have been challenged with....
>
> I will have up to 6 remote databases and I want them all to update a
> single master database in a company with multiple production plants.
> The remote databases will just have active work in a plant and only the
> work that is in that particular plant. I would like the master
> database to have all information from the plants. Ideally, the remote
> plants will update the master database once an hour (consisting of new
> inserts of orders coming into the plant and updated records as work
> moves through the plant). Once work ships from a plant, I want to purge
> it off the remote plant database, yet keep it on the master.
> It seems with replication, if I delete records at a plant, it will
> delete on the master, which is not what I want. The master is
> basically the database customer service will use and needs active
> status on work in the plants and would contain a couple of years of
> information. The remote plant databases have just the data they need
> and our optimized. A remote database has 20 tables, with multiple
> tables with 1 to 20 million records actively inserted/udated each day.
> The schema of the master is identical to the plants and all keys at
> each plant are guaranteed unique.
> Any ideas would be greatly appreciated, as I am currently contemplating
> using bcp in an automated fashion and anticipating a nightmare of
> keeping referential integrity.
> Regards
>
|||Thanks...
My initial thoughts were a bcp dump, zipping the data, sending it over
the WAN, and unzipping then loading it with update/insert SPs. bcp is
incredibly fast, but this strategy requires a lot of management
applications written to ensure the data gets to the master and there
might be loss of some referential integrity as each bcp command would
dump a table at a different time interval (that would be fixed in the
next hourly update). I am intrigued by the replication strategy
because of it's ease of use.
Assuming I have the distributon on the master, what is the performance
impact on the plant databases, assuming a publishing every hour. I am
concerned that the overhead of a replication scheme is vastly greater
than a bcp dump.
What is going on with the replication and how do people set this up. I
guess I was thinking of each plant's database dumping it's repl data on
a remote share over a WAN on the distribution server. I was thinking
the Master would reside on the same server as the distribution (why not
take advantage of loading the data off of a local disk). bw, I would
rather take slowness on the master than in a production facility.
Also...what's the overhead of the replication dump, is it similar to a
log? Given a WAN is down, would sql recover and recopy the replication
data when the WAN came backup?
Also, is this information in any of the replication books out there
(I.E. enterprise strategies for moving data) with pros and cons of
different methods.

replication conflicts for 2 tables

Hi,
we are using merge replication between remote sites and
our central office. couple months ago we had a situation
where we had to insert some records and update other
records with these inserted records and then delete the
inserted records. Then we reinserted these records again
without replicating the deletes to our remote sites.
by doing this we had lots of conflicts.
I mannually deleted replicated and reinserted the records
again.
all other sites are fine but 2 of our sites, which were
disconnected during the delete replication did not get the
deleted records and they still shows conflicts every day
when they replicate. even though these records are not
being edited at all. For some reason they get marked for
replication and shows up in conflicts.
we don't care if those changes doesn't get replicated to
the remote sites becos they don't need those changes. how
do I stop them to show up in conflicts.
thanks
Kiran
did you resolve these conflicts using the conflict viewer? This is the
preferred way of solving this problem?
"Kiran" <anonymous@.discussions.microsoft.com> wrote in message
news:16bc201c41752$0defc130$a101280a@.phx.gbl...
> Hi,
> we are using merge replication between remote sites and
> our central office. couple months ago we had a situation
> where we had to insert some records and update other
> records with these inserted records and then delete the
> inserted records. Then we reinserted these records again
> without replicating the deletes to our remote sites.
> by doing this we had lots of conflicts.
> I mannually deleted replicated and reinserted the records
> again.
> all other sites are fine but 2 of our sites, which were
> disconnected during the delete replication did not get the
> deleted records and they still shows conflicts every day
> when they replicate. even though these records are not
> being edited at all. For some reason they get marked for
> replication and shows up in conflicts.
> we don't care if those changes doesn't get replicated to
> the remote sites becos they don't need those changes. how
> do I stop them to show up in conflicts.
> thanks
> Kiran
sql

Replication between 2 or more SQL Express databases

Problem description
There is one central SQL Express database. And one (or more) SQL Express
database(s) on remote locations. This approach is mandatory due to some
application features later-on.
The local database(s) on the remote location(s) will act as a sort of backup
in case there is no network connection. Meaning that the data is stored
locally at all times. And moved to the central database once the network
connection is on.
Updates to the local database(s) should trigger a process where all data is
moved to the central database if there is a network connection. So for now,
it’s a one way stream: remote to central.
This approach gives us the option to delay the moves - if needed. For
example, the daily data is kept local and moved to the central site over
night. Which is a good thing to have if network resources are limited during
office hours.
Solution
To make this happen, I was thinking allong the lines of using triggered
stored procedures.
Where a local database update triggers a stored procedure that checks the
network connection and performs the move to the central database.
If there is more than one record in the remote database, all records are
moved to the central database. Also, an entry should be added to a log-file.
If the network connection is not there for whatever reason, an entry should
be written in a log-file stating that there was no connection to the central
database.
Options
Another way of solving this is using RMO-based publications and subscribers.
Where the database on the remote locations are publishers. And the central
database are subscribers. However, according to Microsoft:
- SQL Express can only act as a subscriber.
- Data is copied. And not moved.
According to the SQL-BOL, the first limitation doesn’t exist when using
programmatic, transactional replication.
However, the second needs to be solved as well. And in the examples of
SQL-BOL, this is not mentioned. At least not that I’m aware of.
There are some advantages using RMO. For example deploying a new version of
the application. Or deploying an updated database schema. Please let me know
if this is proven to be really usefull. If so, this would be the preferred
method – provided that the limitations mentioned earlier are solved. And if
using this method, I would prefer stored procedures or Visual Basic for
programming this.
Help wanted
Since I’m a newbie on these replication matters, I would like some help with
this.
Who is willing to help with examples and suggestions?
Sofar, I’ve been able to:
- Install SQL Express with network connections enabled
- Running the Management Studio and create the data model I would like to use
- Add data manually and via an ODBC connection (using a system wide DSN).
- Run SQL select commands against the added data.
So the infrastructure is up and running….
firing triggers over the network is not scalable, as there is significant
latency involved for each trigger firing. For a batch operation it is
painful. Your transactions will also hang for up to 20 seconds if the
connection is down.
You might want to look at SSIS (Integration Services) or perhaps even bcp
for what you are trying to do.
You might also want to upgrade from Express to Standard so you can do
transactional replication which will do exactly what you are trying to do.
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
"Will" <Will@.discussions.microsoft.com> wrote in message
news:474B4797-1811-4ADC-8576-0137A4FCBAF9@.microsoft.com...
> Problem description
> --
> There is one central SQL Express database. And one (or more) SQL Express
> database(s) on remote locations. This approach is mandatory due to some
> application features later-on.
> The local database(s) on the remote location(s) will act as a sort of
> backup
> in case there is no network connection. Meaning that the data is stored
> locally at all times. And moved to the central database once the network
> connection is on.
> Updates to the local database(s) should trigger a process where all data
> is
> moved to the central database if there is a network connection. So for
> now,
> it's a one way stream: remote to central.
> This approach gives us the option to delay the moves - if needed. For
> example, the daily data is kept local and moved to the central site over
> night. Which is a good thing to have if network resources are limited
> during
> office hours.
> Solution
> --
> To make this happen, I was thinking allong the lines of using triggered
> stored procedures.
> Where a local database update triggers a stored procedure that checks the
> network connection and performs the move to the central database.
> If there is more than one record in the remote database, all records are
> moved to the central database. Also, an entry should be added to a
> log-file.
> If the network connection is not there for whatever reason, an entry
> should
> be written in a log-file stating that there was no connection to the
> central
> database.
> Options
> Another way of solving this is using RMO-based publications and
> subscribers.
> Where the database on the remote locations are publishers. And the central
> database are subscribers. However, according to Microsoft:
> - SQL Express can only act as a subscriber.
> - Data is copied. And not moved.
> According to the SQL-BOL, the first limitation doesn't exist when using
> programmatic, transactional replication.
> However, the second needs to be solved as well. And in the examples of
> SQL-BOL, this is not mentioned. At least not that I'm aware of.
> There are some advantages using RMO. For example deploying a new version
> of
> the application. Or deploying an updated database schema. Please let me
> know
> if this is proven to be really usefull. If so, this would be the preferred
> method - provided that the limitations mentioned earlier are solved. And
> if
> using this method, I would prefer stored procedures or Visual Basic for
> programming this.
> Help wanted
> --
> Since I'm a newbie on these replication matters, I would like some help
> with
> this.
> Who is willing to help with examples and suggestions?
> Sofar, I've been able to:
> - Install SQL Express with network connections enabled
> - Running the Management Studio and create the data model I would like to
> use
> - Add data manually and via an ODBC connection (using a system wide DSN).
> - Run SQL select commands against the added data.
> So the infrastructure is up and running..
>
|||Hi Hilary,
Thanks for your support and feedback. I really do appreciate this!!!

> firing triggers over the network is not scalable, as there is significant
> latency involved for each trigger firing. For a batch operation it is
> painful. Your transactions will also hang for up to 20 seconds if the
> connection is down.
Mmm - sounds like we have a different understanding of the term trigger.
I would like to use triggers on the remote databases - not the central one.
As a result, triggers are not travelling across the network.

> You might want to look at SSIS (Integration Services) or perhaps even bcp
> for what you are trying to do.
I looked at SSIS. That would require
I'm not familiar with BCP. But it looks like a bulk COPY tool.
How would this help in MOVING the data?

> You might also want to upgrade from Express to Standard so you can do
> transactional replication which will do exactly what you are trying to do.
Do you mean replace Express with standaard on the remote side?
On the central side? Or both?
Keep in mind that SQL Express on the remote sites needs to run on
Workstations.
Ans therefor requires a light footprint.
Will
|||Answers inline.
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
"Will" <Will@.discussions.microsoft.com> wrote in message
news:E6201678-BFD9-4290-ABAC-1D7A5F6E1962@.microsoft.com...
> Hi Hilary,
> Thanks for your support and feedback. I really do appreciate this!!!
>
> Mmm - sounds like we have a different understanding of the term trigger.
> I would like to use triggers on the remote databases - not the central
> one.
> As a result, triggers are not travelling across the network.
>
> I looked at SSIS. That would require
> I'm not familiar with BCP. But it looks like a bulk COPY tool.
> How would this help in MOVING the data?
>
it doesn't move data, it copies it row by row. I know of no technology
which actually moves that, all copy it and you have to delete it yourself on
the source.

> Do you mean replace Express with standaard on the remote side?
> On the central side? Or both?
> Keep in mind that SQL Express on the remote sites needs to run on
> Workstations.
> Ans therefor requires a light footprint.
In retrospect you will probably need a code solution. Put a timestamp on
your tables which you can use to determine which rows have changed since the
last time you "moved" data. Anything greater than the timestamp the last
time you polled must be moved.
You will probably be able to use any version of SQL Server for this.
> --
> Will
>

Replication and use of Remote Server

When Replication is configured it creates a remote server connection. Can it
be configured to use Linked Server instead? Linked server seems to have all
the same capability as Remote Server (and more).
LMK
In SQL 2005 they are all linked servers. IIRC it can, you have to give it
the name of distr_admin. Drill down in remote servers to determine what the
name should be.
Why do you want to do this?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"LMK" <LMK@.discussions.microsoft.com> wrote in message
news:6DD94C8B-7AB8-463D-A4DB-CA42A3C5E7B1@.microsoft.com...
> When Replication is configured it creates a remote server connection. Can
> it
> be configured to use Linked Server instead? Linked server seems to have
> all
> the same capability as Remote Server (and more).
> --
> LMK
|||In this same server, we have a separate true need for a linked server
pointing back to the same master server. I cannot create a linked server with
the same name as a remote server. Therefore if I can change the remote server
for rep to a linked server instead, I have solved both problems. I am on
Win2000. So are you saying that I cannot make this change to Linked Server in
Win2000?
LMK
"Hilary Cotter" wrote:

> In SQL 2005 they are all linked servers. IIRC it can, you have to give it
> the name of distr_admin. Drill down in remote servers to determine what the
> name should be.
> Why do you want to do this?
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> 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
>
> "LMK" <LMK@.discussions.microsoft.com> wrote in message
> news:6DD94C8B-7AB8-463D-A4DB-CA42A3C5E7B1@.microsoft.com...
>
>

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 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 direct updating in SQL 2000

I have taken over the support over a database in sql 2000 that has 10+ remote users that synchronise each day. However it also has 30+ users who are directly updating the data in the live database on the server.

One of these users is entering data directly upon the database on the server but the new rows are being placed in the conflict table somehow!!

Does anybody have any ideas about how this could be happening ?

Is it ok to have users directly updating on the server and users synchronising ?

I would appreciate any help!!

Thanks.

If a change causes a conflict, then it will be placed in the conflict tables. YOu can look at the Conflict Viewer to determine what columns/rows are causing conflicts.

I assume this is merge replication? Users can make changes at publisher or subscriber, it is totally up to you to decide where to make changes.

Replication advice

Hello,
I have 30 remote WinXP sites connected to a Win 2K3 server via VPN.
Each remote site runs MSDE. Basically, they are automated data aquisition
machines recording into a DB about 200K of data every 15 minutes.
The data at each remote site needs to be replicated into its own DB on the
Win 2K3 server on a regular basis, hopefully within 1 or 2 hours of being
first recorded..
What form of replication would be recommended for this scenario?
Thank you
Unfortunately MSDE cannot be a transactional publisher which is the best fit
for what you are trying to do. What you will have to do is use merge
replication with the with the exchangetype being upload only.
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
"MikeH" <MikeH@.community.nospam> wrote in message
news:1AD6F4E7-B7B0-412E-BA9F-D05B7BE6168F@.microsoft.com...
> Hello,
> I have 30 remote WinXP sites connected to a Win 2K3 server via VPN.
> Each remote site runs MSDE. Basically, they are automated data aquisition
> machines recording into a DB about 200K of data every 15 minutes.
> The data at each remote site needs to be replicated into its own DB on the
> Win 2K3 server on a regular basis, hopefully within 1 or 2 hours of being
> first recorded..
> What form of replication would be recommended for this scenario?
> Thank you

replication 18483 eroor

hi all...
I have a little problem.
"18483 - could not connect to server 'Newname' because distributor_admin is
not defined as a remote login at the server."
Mehmet,
Try (using 'Newname')
Use Master
go
Select @.@.Servername
This should return your current server name but if it
returns NULL then try:
Use Master
go
Sp_DropServer 'OldName'
GO
Use Master
go
Sp_Addserver 'NewName', 'local'
GO
Stop and Start SQL Services
If this is not the solution, please let me know if you are using IP
addresses for registered servers in Enterprise Manager.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication - sp_MSget_subscription_guid impossible

We currently have a pull transactional subscription running from a remote 'PublicationServer' in another country to our local server.

After restarting our fire wall we get the following error message:
"The process could not execute '{call sp_MSget_subscription_guid(16)}' on 'PublicationServer'."

This message is followed by another error message: "Another distribution agent for the subscription(s) is running.", although nothing was changed to the configuration and no SQL processes were started or restarted.

When we restart the distribution job manually it runs as if nothing happened.

Does anyone know what exactly caused the failure, and how to prevent it ?

PhilipQuit restarting your firewall ?

I really don't have a good answer for this question. Sometimes after an unexpected failure, the simplest answer is just to manually restart what won't start automagically.

-PatP

Replication

I was working on a project that use local and remote SQL server. In order to keep the database up-to-date I wanted to implement replication on the SQL servers. But unfortunately thetransaction replication which meet my requirement best is disabled on the replication configuration module (snapshoot and merge replications are active). Is there any way I can make the transaction replication enabled. I know it was supposed to be enabled by default. I’m using Windows 2003 server and SQL server 2000.

Sincerely

Do you mean you can't select the Transactional Replication as Replication Type when configure Publication?|||Yes, that is what i mean.|||Sorry I haven't heard of such issue. If you have no better choice, you may reinstall the client tools to see whether it helps.

Replicating Permissions

My reports are currently configured so that only certain users on the
domain can access certain reports. I have installed another server at
a remote location that will need to have the same permissions as the
first one. Is there a way to replicate the security settings without
having to set the permissions manually each time?
Is there a security configuration file somewhere on the first server
that i could move over to the second, since they are pretty much the
same?
Thank you!You may want to check the following tool courtesy of Jasper Smith:
http://www.sqldbatips.com/showarticle.asp?ID=62
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"muris" <rmuris@.hotmail.com> wrote in message
news:1113533808.430998.255460@.f14g2000cwb.googlegroups.com...
> My reports are currently configured so that only certain users on the
> domain can access certain reports. I have installed another server at
> a remote location that will need to have the same permissions as the
> first one. Is there a way to replicate the security settings without
> having to set the permissions manually each time?
> Is there a security configuration file somewhere on the first server
> that i could move over to the second, since they are pretty much the
> same?
> Thank you!
>|||Thanks for your Reply. The app you refered me to helps me replicate
the reports and user roles to multiple servers, but it does not
replicate the security permissions for each folder nor the report. Is
there a script that can accomplish this task?
Thanks!|||Jasper Smith may add this kind of functionality to the tool in a future
release.
On RS 2000 you would have to do this through the SOAP API (ListChildren,
GetProperties, GetPermissions, etc.)
The Management Studio for the upcoming SQL Server 2005 release of Reporting
Services will allow you to generate a script to capture that state and then
apply it to another server.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"muris" <rmuris@.hotmail.com> wrote in message
news:1113572435.510884.55430@.z14g2000cwz.googlegroups.com...
> Thanks for your Reply. The app you refered me to helps me replicate
> the reports and user roles to multiple servers, but it does not
> replicate the security permissions for each folder nor the report. Is
> there a script that can accomplish this task?
> Thanks!
>