pivot information: replication

Showing posts with label replication. Show all posts

Monday, March 26, 2012

please help -- 512 error when generating replication script

Hi,

I'm trying to script out my replication objects using
the 'Generate SQL Script...' option under Tools >
Replication in Enterprise Manager. Under 'Replication
components to script', I check 'Distributor properties'
and 'Publications in these databases:' and choose all
databases listed. I get a 512 error:

Error 512: Subquery returned more than 1 value. This is
not permitted when the subquery follows =, !=, <, <=, >,
>= or when the subquery is used as an expression.

The server is 2000 sp2, and the Ent Mgr client is 2000.
Using the same Ent Mgr client to script replication
objects in other 2000 sp2 servers, I don't receive any
errors.

I appreciate any help you can provide.

Thanks,
LB
.Try scripting individually.

Please Help

Friday, March 23, 2012

Please Help

Hi all,
I need to solve a problem with SQL replication, I know very little about it,
and it wasn't me that set it up.
However we have 2 servers both with sql server 2000 Lets say server A & B
server A has been setup as the publisher & distributor with a transaction
push subscription to server B that has been setup as a subscriber.
I want this to work both ways but it doesn't seem to be replicating from
server B to A. Does anybody know what I can look into to check out what's
happening here?
Thanks
Gav> I want this to work both ways but it doesn't seem to be replicating
> from server B to A. Does anybody know what I can look into to check
> out what's happening here?
See Merge Replication|||Are you telling me that Transaction replication only works one way?
Gav
"JTC ^..^" <dave@.(nospam)JazzTheCat.co.uk> wrote in message
news:Xns95DCE2FB8183DdaveJTC@.217.32.252.50...
> > I want this to work both ways but it doesn't seem to be replicating
> > from server B to A. Does anybody know what I can look into to check
> > out what's happening here?
> See Merge Replication|||Unless you use "with updating subscribers", modifications will only be applied one-way. From
publisher -> subscriber. You can make sure that each site only update its own subset of data and let
both be subscribers and subscribers, but be very careful...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Gav" <spam@.spam.com> wrote in message news:uwXgt1X%23EHA.936@.TK2MSFTNGP12.phx.gbl...
> Are you telling me that Transaction replication only works one way?
> Gav
> "JTC ^..^" <dave@.(nospam)JazzTheCat.co.uk> wrote in message
> news:Xns95DCE2FB8183DdaveJTC@.217.32.252.50...
>> > I want this to work both ways but it doesn't seem to be replicating
>> > from server B to A. Does anybody know what I can look into to check
>> > out what's happening here?
>> See Merge Replication
>|||Sorry you have lost me a little bit there... I did say I havn't got much
knowledge in this field, do you have any sources of information on what you
have mentioned here?
Thanks for helping
Gav
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Ose32EY%23EHA.3376@.TK2MSFTNGP12.phx.gbl...
> Unless you use "with updating subscribers", modifications will only be
applied one-way. From
> publisher -> subscriber. You can make sure that each site only update its
own subset of data and let
> both be subscribers and subscribers, but be very careful...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Gav" <spam@.spam.com> wrote in message
news:uwXgt1X%23EHA.936@.TK2MSFTNGP12.phx.gbl...
> > Are you telling me that Transaction replication only works one way?
> >
> > Gav
> >
> > "JTC ^..^" <dave@.(nospam)JazzTheCat.co.uk> wrote in message
> > news:Xns95DCE2FB8183DdaveJTC@.217.32.252.50...
> >> > I want this to work both ways but it doesn't seem to be replicating
> >> > from server B to A. Does anybody know what I can look into to check
> >> > out what's happening here?
> >>
> >> See Merge Replication
> >
> >
>|||I misprinted the last sentence, should be "both be both subscriber and publisher". I don't know
offhand where to find more info on this, but I'd start looking in Books Online.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Gav" <spam@.spam.com> wrote in message news:OdQCosY%23EHA.3472@.TK2MSFTNGP14.phx.gbl...
> Sorry you have lost me a little bit there... I did say I havn't got much
> knowledge in this field, do you have any sources of information on what you
> have mentioned here?
> Thanks for helping
> Gav
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:Ose32EY%23EHA.3376@.TK2MSFTNGP12.phx.gbl...
>> Unless you use "with updating subscribers", modifications will only be
> applied one-way. From
>> publisher -> subscriber. You can make sure that each site only update its
> own subset of data and let
>> both be subscribers and subscribers, but be very careful...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Gav" <spam@.spam.com> wrote in message
> news:uwXgt1X%23EHA.936@.TK2MSFTNGP12.phx.gbl...
>> > Are you telling me that Transaction replication only works one way?
>> >
>> > Gav
>> >
>> > "JTC ^..^" <dave@.(nospam)JazzTheCat.co.uk> wrote in message
>> > news:Xns95DCE2FB8183DdaveJTC@.217.32.252.50...
>> >> > I want this to work both ways but it doesn't seem to be replicating
>> >> > from server B to A. Does anybody know what I can look into to check
>> >> > out what's happening here?
>> >>
>> >> See Merge Replication
>> >
>> >
>>
>|||Try to look at
http://www.microsoft.com/sql/evaluation/features/replication.asp or Search
Books online for Replication. That will give you an initial knowledge about
Replication.
Regards
Steen
Gav wrote:
> Are you telling me that Transaction replication only works one way?
> Gav
> "JTC ^..^" <dave@.(nospam)JazzTheCat.co.uk> wrote in message
> news:Xns95DCE2FB8183DdaveJTC@.217.32.252.50...
>> I want this to work both ways but it doesn't seem to be replicating
>> from server B to A. Does anybody know what I can look into to check
>> out what's happening here?
>> See Merge Replication

Please check this replication error..

I tried to replicate between SVRPOS01 and SVRPOS02.
SVRPOS01 is publisher and distributor.
Replication is Merge replication.
But, after snapshot agent ran, the following error comes out and merge agent doesn't do merge replication.
When configure replication I choose option initialize schema.., and in SVRPOS02 I just create empty DB.
Most of time this works... but not in this time..
SVRPOS02 doesn't have data replicated...
Please reply any idea of following error, and solution if you have any..
Thank you.

<Error message>
The schema script '\\SVRPOS01\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\unc\SVRPOS01_POS_POSPublicat ion\20040706003309\v_Item_Old_232.sch' could not be propagated to the subscriber.

<Error Detail>
The schema script '\\SVRPOS01\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\unc\SVRPOS01_POS_POSPublicat ion\20040706003309\v_Item_Old_232.sch' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
----------------------------------
Unable to replicate a view or function because the referenced objects or columns are not present on the Subscriber.
(Source: SVRPOS02 (Agent); Error number: 0)
----------------------------------
Invalid object name 'POSLOC.dbo.BARCODE_MATCH'.
(Source: SVRPOS02 (Data source); Error number: 208)
----------------------------------You have to script the structure of the publishing database and apply to the subscriber before the snapshot agent runs for the first time.|||By any chance, does that view contain some sort of cross-database query? Then you need to make sure that database is also present on the subscriber.

Tuesday, March 20, 2012

Planning replication

Good morning to all ...
This is my scenario:
1. We will have a central publisher
2. We will have SQL Subscribers
3. The data can be changed on the subscriber and in the publisher.
4. The central publisher will have 1 database that acts like a central
repository
for all the other suscription servers.
5. The data changes performed on the central database that belong to a
particular
server only should be replicated to that server.
Can this be done using replication ?
I have been reading about replication and "maybe" merge replication could be
a solution, but I
am not sure if the horizontal filtering will satisfy all my requirements.
Please I need some guidelines to perform this process
Thanks for any contribution,
Raul
Raul,
this can be achieved using merge. You might want to read up on dynamic
filters, as you need to filter the data depending on the subscriber. As well
as the details in BOL, you can use -HOSTNAME in the merge agent's exe
parameters to partition the data.
HTH,
Paul Ibison
|||"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uzqUUNzcEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Raul,
> this can be achieved using merge. You might want to read up on dynamic
> filters, as you need to filter the data depending on the subscriber. As
well
> as the details in BOL, you can use -HOSTNAME in the merge agent's exe
> parameters to partition the data.
> HTH,
> Paul Ibison
>
Thank you for your answer Paul ...
Please help, I have another question, What if a table in my database (The
same on publisher and subscribers) has an identity column defined, and the
same RecordID is replicated to my central server from two different
subscribers ? I have read that assigning a range for the identity fields is
one possible solution however this delimited my solution scalability, There
is another way to take care of this issue ?
Thank you,
Raul
|||Raul,
if the identity column is the PK column, then the values can't be allowed to
overlap but if it is part of a multi-column then matches are not necessarily
a problem. In the first case you can have SQL server assign ranges or
manually manage them yourself. Michael Hotek has outlined a neat algorithm
to ensure no overlaps for several subscribers, using odd and even ranges
with/without negative values etc. Either way is possible for a lot of
subscribers so isn't inherantly unscalable. Another thread today deals with
the pros and cons of guids vs identies, but generally identities are
preferred.
HTH,
Paul Ibison

planning a replication

hallo
we have a sql2000 in the headquarter, and 3 new remote branches opening in few weeks with no sql servers installed yet.
We plan to setup a merge replica. The headquarter will have the highest activity on the replicated tables.
Shall we use all SQL2000 in the remote branches? Or could we use SQL2005, using a 2005 as a publisher and distributor?
TIA

If possible, upgrade all your nodes to SQL 2005. Merge replication performs and scales much better with the new pre-computed partitions. If this is not possible, then the only supported configuration is that the version of the distributor >= version of the publisher >= version of the subscriber. You can find more info about this in topic Using Multiple Versions of SQL Server in a Replication Topology".

|||ok thanks.
we're not going to upgrade the only sql2000 server we have, but i'd prefere to use sql2005 in the remote branches: in this scenario, i could set one of the 2005 as distributor and publisher.
This would be in contrast with the network topology, that centers everything in the main plant; BTW there will not be a big traffic of replicated data: a theoretical maximum of about 10 records/minute.

Monday, March 12, 2012

placement of Analysis service? on cluster or lone server?

Hi, we have an active/passive cluster which hosts our production database.
Transactional replication is being made from the production to a 'reporting'
database residing on a lone server. We will need to install Analysis service
for the construction of cubes.
I was wondering where Analysis service should be installed?
Is is ok to install it on the lone server and have it use the data from the
reporting database (which is filled via transactional replication)? Will
Analysis service have a problem with this based on the fact that it is
reading a read only database which doesnt have primary keys in the tables?
OR, should analysis service be installed on the cluster? Is it cluster
aware?
At this stage we are thinking of only running the cubes at night to generate
the data for export to reporting service.
Would it then be a good idea to install reporting service on this same lone
server?
Any insight would be most appreciated!
Cheers, john
If that is the case, you can't possibly be running transactional
replication.
The "reporting" database is LOGICALLY read-only, not physically read-only.
This database also MUST have all of the primary keys in place on the tables,
since it is impossible to replicate a table with transactional replication
if the table does not have a primary key. This primary key exists at both
the publisher and the subscriber.
Analysis Services is not going to write to your tables when building cubes,
so it does not care if the tables are physically read-only, logically
read-only, or read-write.
Where you place AS is entirely up to you. You can install it on the
stand-alone server and you can install it in the cluster. The question you
need to ask is what level of availability do you need for AS. If it needs
to be available as much as possible, even through a hardware failure, then
it should be installed in the cluster. If not, it should be installed on
the stand-alone machine.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"john clarke" <jclarke@.nospam.com> wrote in message
news:%23QyI71JDGHA.688@.TK2MSFTNGP11.phx.gbl...
> Hi, we have an active/passive cluster which hosts our production database.
> Transactional replication is being made from the production to a
> 'reporting'
> database residing on a lone server. We will need to install Analysis
> service
> for the construction of cubes.
> I was wondering where Analysis service should be installed?
> Is is ok to install it on the lone server and have it use the data from
> the
> reporting database (which is filled via transactional replication)? Will
> Analysis service have a problem with this based on the fact that it is
> reading a read only database which doesnt have primary keys in the tables?
> OR, should analysis service be installed on the cluster? Is it cluster
> aware?
> At this stage we are thinking of only running the cubes at night to
> generate
> the data for export to reporting service.
> Would it then be a good idea to install reporting service on this same
> lone
> server?
> Any insight would be most appreciated!
> Cheers, john
>
>

Friday, March 9, 2012

PK violation error during replication

While replicating some tables into another sql server for
DB sync., I run into a problem as follows;
================================================== =========
Violation of PRIMARY KEY
constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
duplicate key in object '#65EA00FF'.
Violation of PRIMARY KEY
constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
duplicate key in object '#65EA00FF'.
(Source: TUBE\TUBE2 (Data source); Error number: 2627)
================================================== =========
At MSDN, I found it's a kind of sql server bug.
(See, http://support.microsoft.com/default.aspx?scid=kb;en-
us;813494)
Unfortunately, to solve it, contact to Microsoft was
required and it cost some money & time to get the hot fix
from MS headquarter.-Currently, I'm in Asia.
So, I'd like to ask you guys to e-mail
(lovelydovey@.msn.com) me the hot fix, if you have. Or, if
there's another way to solve this problem, pls, tell me
the rope..!
e-mail : lovelydovey@.msn.com
Your answer would be appreciated!
Do the service pack... Even if it is some trouble.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Park" <anonymous@.discussions.microsoft.com> wrote in message
news:268e101c4634e$4f0ff020$a601280a@.phx.gbl...
> While replicating some tables into another sql server for
> DB sync., I run into a problem as follows;
>
> ================================================== =========
> Violation of PRIMARY KEY
> constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
> duplicate key in object '#65EA00FF'.
> Violation of PRIMARY KEY
> constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
> duplicate key in object '#65EA00FF'.
> (Source: TUBE\TUBE2 (Data source); Error number: 2627)
> ================================================== =========
>
> At MSDN, I found it's a kind of sql server bug.
> (See, http://support.microsoft.com/default.aspx?scid=kb;en-
> us;813494)
> Unfortunately, to solve it, contact to Microsoft was
> required and it cost some money & time to get the hot fix
> from MS headquarter.-Currently, I'm in Asia.
> So, I'd like to ask you guys to e-mail
> (lovelydovey@.msn.com) me the hot fix, if you have. Or, if
> there's another way to solve this problem, pls, tell me
> the rope..!
> e-mail : lovelydovey@.msn.com
> Your answer would be appreciated!
>

PK violation error during replication

While replicating some tables into another sql server for
DB sync., I run into a problem as follows;
========================================
===================
Violation of PRIMARY KEY
constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
duplicate key in object '#65EA00FF'.
Violation of PRIMARY KEY
constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
duplicate key in object '#65EA00FF'.
(Source: TUBE\TUBE2 (Data source); Error number: 2627)
========================================
===================
At MSDN, I found it's a kind of sql server bug.
(See, http://support.microsoft.com/default.aspx?scid=kb;en-
us;813494)
Unfortunately, to solve it, contact to Microsoft was
required and it cost some money & time to get the hot fix
from MS headquarter.-Currently, I'm in Asia.
So, I'd like to ask you guys to e-mail
(lovelydovey@.msn.com) me the hot fix, if you have. Or, if
there's another way to solve this problem, pls, tell me
the rope..!
e-mail : lovelydovey@.msn.com
Your answer would be appreciated!Do the service pack... Even if it is some trouble.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Park" <anonymous@.discussions.microsoft.com> wrote in message
news:268e101c4634e$4f0ff020$a601280a@.phx
.gbl...
> While replicating some tables into another sql server for
> DB sync., I run into a problem as follows;
>
> ========================================
===================
> Violation of PRIMARY KEY
> constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
> duplicate key in object '#65EA00FF'.
> Violation of PRIMARY KEY
> constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
> duplicate key in object '#65EA00FF'.
> (Source: TUBE\TUBE2 (Data source); Error number: 2627)
> ========================================
===================
>
> At MSDN, I found it's a kind of sql server bug.
> (See, http://support.microsoft.com/default.aspx?scid=kb;en-
> us;813494)
> Unfortunately, to solve it, contact to Microsoft was
> required and it cost some money & time to get the hot fix
> from MS headquarter.-Currently, I'm in Asia.
> So, I'd like to ask you guys to e-mail
> (lovelydovey@.msn.com) me the hot fix, if you have. Or, if
> there's another way to solve this problem, pls, tell me
> the rope..!
> e-mail : lovelydovey@.msn.com
> Your answer would be appreciated!
>

PK violation error during replication

While replicating some tables into another sql server for
DB sync., I run into a problem as follows;
=========================================================== Violation of PRIMARY KEY
constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
duplicate key in object '#65EA00FF'.
Violation of PRIMARY KEY
constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
duplicate key in object '#65EA00FF'.
(Source: TUBE\TUBE2 (Data source); Error number: 2627)
===========================================================
At MSDN, I found it's a kind of sql server bug.
(See, http://support.microsoft.com/default.aspx?scid=kb;en-
us;813494)
Unfortunately, to solve it, contact to Microsoft was
required and it cost some money & time to get the hot fix
from MS headquarter.-Currently, I'm in Asia.
So, I'd like to ask you guys to e-mail
(lovelydovey@.msn.com) me the hot fix, if you have. Or, if
there's another way to solve this problem, pls, tell me
the rope..!
e-mail : lovelydovey@.msn.com
Your answer would be appreciated!Do the service pack... Even if it is some trouble.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Park" <anonymous@.discussions.microsoft.com> wrote in message
news:268e101c4634e$4f0ff020$a601280a@.phx.gbl...
> While replicating some tables into another sql server for
> DB sync., I run into a problem as follows;
>
> ===========================================================> Violation of PRIMARY KEY
> constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
> duplicate key in object '#65EA00FF'.
> Violation of PRIMARY KEY
> constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
> duplicate key in object '#65EA00FF'.
> (Source: TUBE\TUBE2 (Data source); Error number: 2627)
> ===========================================================>
> At MSDN, I found it's a kind of sql server bug.
> (See, http://support.microsoft.com/default.aspx?scid=kb;en-
> us;813494)
> Unfortunately, to solve it, contact to Microsoft was
> required and it cost some money & time to get the hot fix
> from MS headquarter.-Currently, I'm in Asia.
> So, I'd like to ask you guys to e-mail
> (lovelydovey@.msn.com) me the hot fix, if you have. Or, if
> there's another way to solve this problem, pls, tell me
> the rope..!
> e-mail : lovelydovey@.msn.com
> Your answer would be appreciated!
>

Monday, March 26, 2012

please help -- 512 error when generating replication script

Please Help

Friday, March 23, 2012

Please Help

Please Help

Please check this replication error..

Tuesday, March 20, 2012

Planning replication

planning a replication

Monday, March 12, 2012

placement of Analysis service? on cluster or lone server?

Friday, March 9, 2012

PK violation error during replication

PK violation error during replication

PK violation error during replication

pivot information

Blog Archive

About Me