Hi,
I am setting up a DataCenter database on SERVER1. my data is residing in
the different databases on SERVER1 as well. I am intending to do a
replication for each of the databases to DataCenter but i believe replication
cannot be done on the same server.
However, i would like the abilities of Replication to update DataCenter
whenever there's modification and new records automatically from the various
databases. How can i acheive this as there's no unique field in the tables of
these databases to allow me ensure that i am able to copy over all the new
records as well as modified records by using queries.
furthermore , all these databases are also replicated databases from
elsewhere , if i create a insert/modify triggers in these databases will it
work ? i.e during replication a record is inserted and will this be
considered a real insertion that will trigger off the triggers ?
Appreciate any advice
tks & rdgs
Hi
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:83E7984A-50AC-4FA2-9541-EB2558EB7905@.microsoft.com...
> Hi,
> I am setting up a DataCenter database on SERVER1. my data is residing in
> the different databases on SERVER1 as well. I am intending to do a
> replication for each of the databases to DataCenter but i believe
> replication
> cannot be done on the same server.
> However, i would like the abilities of Replication to update DataCenter
> whenever there's modification and new records automatically from the
> various
> databases. How can i acheive this as there's no unique field in the tables
> of
> these databases to allow me ensure that i am able to copy over all the new
> records as well as modified records by using queries.
> furthermore , all these databases are also replicated databases from
> elsewhere , if i create a insert/modify triggers in these databases will
> it
> work ? i.e during replication a record is inserted and will this be
> considered a real insertion that will trigger off the triggers ?
> Appreciate any advice
> tks & rdgs
|||Hi ,
Actually it's not a matter of me not able to set up replication but i
don't think Replication can occur on the same server between 2 different
databases as in my case.
So i am wondering if w/o having to write any queries (as the structure does
not allow me to uniquely identify whether a record is a new or modified one)
, can i have something that as automatic as replication in detecting changes
(such as a modified or new record)
I am thinking of using triggers actually ...
Appreciate any advice
tks & rdgs
"Uri Dimant" wrote:
> Hi
> http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
> Replica (Step by step)
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:83E7984A-50AC-4FA2-9541-EB2558EB7905@.microsoft.com...
>
>
Showing posts with label inthe. Show all posts
Showing posts with label inthe. Show all posts
Wednesday, March 21, 2012
replication between same server
replication between same server
Hi,
I am setting up a DataCenter database on SERVER1. my data is residing in
the different databases on SERVER1 as well. I am intending to do a
replication for each of the databases to DataCenter but i believe replicatio
n
cannot be done on the same server.
However, i would like the abilities of Replication to update DataCenter
whenever there's modification and new records automatically from the various
databases. How can i acheive this as there's no unique field in the tables o
f
these databases to allow me ensure that i am able to copy over all the new
records as well as modified records by using queries.
furthermore , all these databases are also replicated databases from
elsewhere , if i create a insert/modify triggers in these databases will it
work ? i.e during replication a record is inserted and will this be
considered a real insertion that will trigger off the triggers ?
Appreciate any advice
tks & rdgsHi
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:83E7984A-50AC-4FA2-9541-EB2558EB7905@.microsoft.com...
> Hi,
> I am setting up a DataCenter database on SERVER1. my data is residing in
> the different databases on SERVER1 as well. I am intending to do a
> replication for each of the databases to DataCenter but i believe
> replication
> cannot be done on the same server.
> However, i would like the abilities of Replication to update DataCenter
> whenever there's modification and new records automatically from the
> various
> databases. How can i acheive this as there's no unique field in the tables
> of
> these databases to allow me ensure that i am able to copy over all the new
> records as well as modified records by using queries.
> furthermore , all these databases are also replicated databases from
> elsewhere , if i create a insert/modify triggers in these databases will
> it
> work ? i.e during replication a record is inserted and will this be
> considered a real insertion that will trigger off the triggers ?
> Appreciate any advice
> tks & rdgs|||Hi ,
Actually it's not a matter of me not able to set up replication but i
don't think Replication can occur on the same server between 2 different
databases as in my case.
So i am wondering if w/o having to write any queries (as the structure does
not allow me to uniquely identify whether a record is a new or modified one)
, can i have something that as automatic as replication in detecting changes
(such as a modified or new record)
I am thinking of using triggers actually ...
Appreciate any advice
tks & rdgs
"Uri Dimant" wrote:
> Hi
> http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
> Replica (Step by step)
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:83E7984A-50AC-4FA2-9541-EB2558EB7905@.microsoft.com...
>
>
I am setting up a DataCenter database on SERVER1. my data is residing in
the different databases on SERVER1 as well. I am intending to do a
replication for each of the databases to DataCenter but i believe replicatio
n
cannot be done on the same server.
However, i would like the abilities of Replication to update DataCenter
whenever there's modification and new records automatically from the various
databases. How can i acheive this as there's no unique field in the tables o
f
these databases to allow me ensure that i am able to copy over all the new
records as well as modified records by using queries.
furthermore , all these databases are also replicated databases from
elsewhere , if i create a insert/modify triggers in these databases will it
work ? i.e during replication a record is inserted and will this be
considered a real insertion that will trigger off the triggers ?
Appreciate any advice
tks & rdgsHi
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:83E7984A-50AC-4FA2-9541-EB2558EB7905@.microsoft.com...
> Hi,
> I am setting up a DataCenter database on SERVER1. my data is residing in
> the different databases on SERVER1 as well. I am intending to do a
> replication for each of the databases to DataCenter but i believe
> replication
> cannot be done on the same server.
> However, i would like the abilities of Replication to update DataCenter
> whenever there's modification and new records automatically from the
> various
> databases. How can i acheive this as there's no unique field in the tables
> of
> these databases to allow me ensure that i am able to copy over all the new
> records as well as modified records by using queries.
> furthermore , all these databases are also replicated databases from
> elsewhere , if i create a insert/modify triggers in these databases will
> it
> work ? i.e during replication a record is inserted and will this be
> considered a real insertion that will trigger off the triggers ?
> Appreciate any advice
> tks & rdgs|||Hi ,
Actually it's not a matter of me not able to set up replication but i
don't think Replication can occur on the same server between 2 different
databases as in my case.
So i am wondering if w/o having to write any queries (as the structure does
not allow me to uniquely identify whether a record is a new or modified one)
, can i have something that as automatic as replication in detecting changes
(such as a modified or new record)
I am thinking of using triggers actually ...
Appreciate any advice
tks & rdgs
"Uri Dimant" wrote:
> Hi
> http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
> Replica (Step by step)
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:83E7984A-50AC-4FA2-9541-EB2558EB7905@.microsoft.com...
>
>
Monday, February 20, 2012
replicating MS Great Plains database
Hi, I hope comeone could help with an additional query i have.
I submitted a post just previously asking how I can configure replication in
the situation where I have a database (call it db1) and a copy of db1 (call
it db2). db2 was created via:
1. detach db1
2. make a copy of db1 (call it db2)
3. attach db2 to new server
Replication is set up in such a way so that db1 replicated to db2 (via
transactional - or whatever is best) and after a few days db2 becomes the
new replacement for db1.
My query is, will this work if db1 is a great plains database? I know great
plains uses a number of databases for its configuration.
How should i set this up? Any help most appreciated!
Cheers,
Jen
That's a difficult question to answer. Some application will write server
specific information to the database and it will be difficult to have the
application use the replicated database.
I would test to see if the application is sensitive to the copied database
first.
For disaster recovery solutions similar to what you are describing
replication is not the best option as it does not do automatic failover. Log
Shipping is the best solution as every object is copied, even system
objects.
If you must use replication for this you have to
1) make sure every table has a PK
2) make sure all constraints, triggers and identity columns are marked not
for replication
3) make sure you use different identity seeds on each side (odd on one side
even on the other) and use an increment of 2
4) use DBCC checkident(tablename, reseed, #) on each side on the identity
tables to make sure that the tables with odd seed will all have odd values
for their current or next value, and make sure all tables on the other side
with the even seed will all have even values for their current or next
value.
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
"jen" <jc@.nospam> wrote in message
news:OnlBhSw$FHA.3096@.tk2msftngp13.phx.gbl...
> Hi, I hope comeone could help with an additional query i have.
> I submitted a post just previously asking how I can configure replication
> in the situation where I have a database (call it db1) and a copy of db1
> (call it db2). db2 was created via:
> 1. detach db1
> 2. make a copy of db1 (call it db2)
> 3. attach db2 to new server
> Replication is set up in such a way so that db1 replicated to db2 (via
> transactional - or whatever is best) and after a few days db2 becomes the
> new replacement for db1.
> My query is, will this work if db1 is a great plains database? I know
> great plains uses a number of databases for its configuration.
> How should i set this up? Any help most appreciated!
> Cheers,
> Jen
>
I submitted a post just previously asking how I can configure replication in
the situation where I have a database (call it db1) and a copy of db1 (call
it db2). db2 was created via:
1. detach db1
2. make a copy of db1 (call it db2)
3. attach db2 to new server
Replication is set up in such a way so that db1 replicated to db2 (via
transactional - or whatever is best) and after a few days db2 becomes the
new replacement for db1.
My query is, will this work if db1 is a great plains database? I know great
plains uses a number of databases for its configuration.
How should i set this up? Any help most appreciated!
Cheers,
Jen
That's a difficult question to answer. Some application will write server
specific information to the database and it will be difficult to have the
application use the replicated database.
I would test to see if the application is sensitive to the copied database
first.
For disaster recovery solutions similar to what you are describing
replication is not the best option as it does not do automatic failover. Log
Shipping is the best solution as every object is copied, even system
objects.
If you must use replication for this you have to
1) make sure every table has a PK
2) make sure all constraints, triggers and identity columns are marked not
for replication
3) make sure you use different identity seeds on each side (odd on one side
even on the other) and use an increment of 2
4) use DBCC checkident(tablename, reseed, #) on each side on the identity
tables to make sure that the tables with odd seed will all have odd values
for their current or next value, and make sure all tables on the other side
with the even seed will all have even values for their current or next
value.
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
"jen" <jc@.nospam> wrote in message
news:OnlBhSw$FHA.3096@.tk2msftngp13.phx.gbl...
> Hi, I hope comeone could help with an additional query i have.
> I submitted a post just previously asking how I can configure replication
> in the situation where I have a database (call it db1) and a copy of db1
> (call it db2). db2 was created via:
> 1. detach db1
> 2. make a copy of db1 (call it db2)
> 3. attach db2 to new server
> Replication is set up in such a way so that db1 replicated to db2 (via
> transactional - or whatever is best) and after a few days db2 becomes the
> new replacement for db1.
> My query is, will this work if db1 is a great plains database? I know
> great plains uses a number of databases for its configuration.
> How should i set this up? Any help most appreciated!
> Cheers,
> Jen
>
Subscribe to:
Posts (Atom)