I want to know how to obtain an encrypted communication
between two SQL Servers using Replication.
I saw that using SSL is posible to grant secure
communication between client an server, but how can i
encrypt communication between two servers?
Hector,
as far as I understand, The SSL encryption applies to all inter-computer communication protocols supported by SQL Server 2000. Alternatively you can use Multi-protocol with encryption facility, for more information review books online.
Regards,
Paul Ibison
Showing posts with label replication. Show all posts
Showing posts with label replication. Show all posts
Monday, March 26, 2012
Friday, March 23, 2012
how to enable replication from 2000 to 2005
Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.server:423927
I have never done replication before, so treat me like a novice, even though
I'm otherwise familiar with SQL Server.
I have a database on a SQL 2000 machine. Soon, I want to port the database
to SQL 2005, but in the meantime, I want to do some testing against our new
2005 box. I thought I should enable replication from the 2000 box to the
2005 box. This will allow us to do queries on each, test the data and
security settings are the same, and then *instantly* transfer the
application to pull from the 2005 box when testing is complete.
1) If the 2005's database starts as blank, will it copy over all existing
data, or just the data for new inserts/updates/deletes?
2) How do I enable replication, and of what type, on each box? I have a
book on the 2005 beta, which helps a little bit, but I'm still pretty lost
on what to set up on both boxes.
3) Will I have to reboot the 2000 box anytime in this process? I can't do
that. It's live 24/7.
4) What happens if the receiving box, the 2005 one, is rebooted? Will it
catch up with that couple minutes of lost data when it is back online?
1. The replication engine will generate a snapshot of the 2000 machine, data
and structure, and apply it to the 2005 machine. Changes will then be sent
from publisher to subscriber. You may need to manually transfer other
objects such as procedures, views, triggers, etc. You will have to transfer
logins and users yourself.
2. There is a replication wizard which can take you through the process.
You should be able to use transactional replication. You'll want to
configure the distributor on the 2005 machine.
3. No, it does not require a reboot.
4. If either the publisher or subscriber goes down, replication will pick up
where it left off. The amount of time to catch up is dependent upon the
volume of data needing to be sent and the bandwidth available to send it.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"HK" <replywithingroup@.notreal.com> wrote in message
news:vMOIf.8366$Jg.7375@.tornado.socal.rr.com...
>I have never done replication before, so treat me like a novice, even
>though
> I'm otherwise familiar with SQL Server.
> I have a database on a SQL 2000 machine. Soon, I want to port the
> database
> to SQL 2005, but in the meantime, I want to do some testing against our
> new
> 2005 box. I thought I should enable replication from the 2000 box to the
> 2005 box. This will allow us to do queries on each, test the data and
> security settings are the same, and then *instantly* transfer the
> application to pull from the 2005 box when testing is complete.
> 1) If the 2005's database starts as blank, will it copy over all existing
> data, or just the data for new inserts/updates/deletes?
> 2) How do I enable replication, and of what type, on each box? I have a
> book on the 2005 beta, which helps a little bit, but I'm still pretty lost
> on what to set up on both boxes.
> 3) Will I have to reboot the 2000 box anytime in this process? I can't
> do
> that. It's live 24/7.
> 4) What happens if the receiving box, the 2005 one, is rebooted? Will it
> catch up with that couple minutes of lost data when it is back online?
>
I have never done replication before, so treat me like a novice, even though
I'm otherwise familiar with SQL Server.
I have a database on a SQL 2000 machine. Soon, I want to port the database
to SQL 2005, but in the meantime, I want to do some testing against our new
2005 box. I thought I should enable replication from the 2000 box to the
2005 box. This will allow us to do queries on each, test the data and
security settings are the same, and then *instantly* transfer the
application to pull from the 2005 box when testing is complete.
1) If the 2005's database starts as blank, will it copy over all existing
data, or just the data for new inserts/updates/deletes?
2) How do I enable replication, and of what type, on each box? I have a
book on the 2005 beta, which helps a little bit, but I'm still pretty lost
on what to set up on both boxes.
3) Will I have to reboot the 2000 box anytime in this process? I can't do
that. It's live 24/7.
4) What happens if the receiving box, the 2005 one, is rebooted? Will it
catch up with that couple minutes of lost data when it is back online?
1. The replication engine will generate a snapshot of the 2000 machine, data
and structure, and apply it to the 2005 machine. Changes will then be sent
from publisher to subscriber. You may need to manually transfer other
objects such as procedures, views, triggers, etc. You will have to transfer
logins and users yourself.
2. There is a replication wizard which can take you through the process.
You should be able to use transactional replication. You'll want to
configure the distributor on the 2005 machine.
3. No, it does not require a reboot.
4. If either the publisher or subscriber goes down, replication will pick up
where it left off. The amount of time to catch up is dependent upon the
volume of data needing to be sent and the bandwidth available to send it.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"HK" <replywithingroup@.notreal.com> wrote in message
news:vMOIf.8366$Jg.7375@.tornado.socal.rr.com...
>I have never done replication before, so treat me like a novice, even
>though
> I'm otherwise familiar with SQL Server.
> I have a database on a SQL 2000 machine. Soon, I want to port the
> database
> to SQL 2005, but in the meantime, I want to do some testing against our
> new
> 2005 box. I thought I should enable replication from the 2000 box to the
> 2005 box. This will allow us to do queries on each, test the data and
> security settings are the same, and then *instantly* transfer the
> application to pull from the 2005 box when testing is complete.
> 1) If the 2005's database starts as blank, will it copy over all existing
> data, or just the data for new inserts/updates/deletes?
> 2) How do I enable replication, and of what type, on each box? I have a
> book on the 2005 beta, which helps a little bit, but I'm still pretty lost
> on what to set up on both boxes.
> 3) Will I have to reboot the 2000 box anytime in this process? I can't
> do
> that. It's live 24/7.
> 4) What happens if the receiving box, the 2005 one, is rebooted? Will it
> catch up with that couple minutes of lost data when it is back online?
>
how to enable replication from 2000 to 2005
Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.server:423927
I have never done replication before, so treat me like a novice, even though
I'm otherwise familiar with SQL Server.
I have a database on a SQL 2000 machine. Soon, I want to port the database
to SQL 2005, but in the meantime, I want to do some testing against our new
2005 box. I thought I should enable replication from the 2000 box to the
2005 box. This will allow us to do queries on each, test the data and
security settings are the same, and then *instantly* transfer the
application to pull from the 2005 box when testing is complete.
1) If the 2005's database starts as blank, will it copy over all existing
data, or just the data for new inserts/updates/deletes?
2) How do I enable replication, and of what type, on each box? I have a
book on the 2005 beta, which helps a little bit, but I'm still pretty lost
on what to set up on both boxes.
3) Will I have to reboot the 2000 box anytime in this process? I can't do
that. It's live 24/7.
4) What happens if the receiving box, the 2005 one, is rebooted? Will it
catch up with that couple minutes of lost data when it is back online?1. The replication engine will generate a snapshot of the 2000 machine, data
and structure, and apply it to the 2005 machine. Changes will then be sent
from publisher to subscriber. You may need to manually transfer other
objects such as procedures, views, triggers, etc. You will have to transfer
logins and users yourself.
2. There is a replication wizard which can take you through the process.
You should be able to use transactional replication. You'll want to
configure the distributor on the 2005 machine.
3. No, it does not require a reboot.
4. If either the publisher or subscriber goes down, replication will pick up
where it left off. The amount of time to catch up is dependent upon the
volume of data needing to be sent and the bandwidth available to send it.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"HK" <replywithingroup@.notreal.com> wrote in message
news:vMOIf.8366$Jg.7375@.tornado.socal.rr.com...
>I have never done replication before, so treat me like a novice, even
>though
> I'm otherwise familiar with SQL Server.
> I have a database on a SQL 2000 machine. Soon, I want to port the
> database
> to SQL 2005, but in the meantime, I want to do some testing against our
> new
> 2005 box. I thought I should enable replication from the 2000 box to the
> 2005 box. This will allow us to do queries on each, test the data and
> security settings are the same, and then *instantly* transfer the
> application to pull from the 2005 box when testing is complete.
> 1) If the 2005's database starts as blank, will it copy over all existing
> data, or just the data for new inserts/updates/deletes?
> 2) How do I enable replication, and of what type, on each box? I have a
> book on the 2005 beta, which helps a little bit, but I'm still pretty lost
> on what to set up on both boxes.
> 3) Will I have to reboot the 2000 box anytime in this process? I can't
> do
> that. It's live 24/7.
> 4) What happens if the receiving box, the 2005 one, is rebooted? Will it
> catch up with that couple minutes of lost data when it is back online?
>
I have never done replication before, so treat me like a novice, even though
I'm otherwise familiar with SQL Server.
I have a database on a SQL 2000 machine. Soon, I want to port the database
to SQL 2005, but in the meantime, I want to do some testing against our new
2005 box. I thought I should enable replication from the 2000 box to the
2005 box. This will allow us to do queries on each, test the data and
security settings are the same, and then *instantly* transfer the
application to pull from the 2005 box when testing is complete.
1) If the 2005's database starts as blank, will it copy over all existing
data, or just the data for new inserts/updates/deletes?
2) How do I enable replication, and of what type, on each box? I have a
book on the 2005 beta, which helps a little bit, but I'm still pretty lost
on what to set up on both boxes.
3) Will I have to reboot the 2000 box anytime in this process? I can't do
that. It's live 24/7.
4) What happens if the receiving box, the 2005 one, is rebooted? Will it
catch up with that couple minutes of lost data when it is back online?1. The replication engine will generate a snapshot of the 2000 machine, data
and structure, and apply it to the 2005 machine. Changes will then be sent
from publisher to subscriber. You may need to manually transfer other
objects such as procedures, views, triggers, etc. You will have to transfer
logins and users yourself.
2. There is a replication wizard which can take you through the process.
You should be able to use transactional replication. You'll want to
configure the distributor on the 2005 machine.
3. No, it does not require a reboot.
4. If either the publisher or subscriber goes down, replication will pick up
where it left off. The amount of time to catch up is dependent upon the
volume of data needing to be sent and the bandwidth available to send it.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"HK" <replywithingroup@.notreal.com> wrote in message
news:vMOIf.8366$Jg.7375@.tornado.socal.rr.com...
>I have never done replication before, so treat me like a novice, even
>though
> I'm otherwise familiar with SQL Server.
> I have a database on a SQL 2000 machine. Soon, I want to port the
> database
> to SQL 2005, but in the meantime, I want to do some testing against our
> new
> 2005 box. I thought I should enable replication from the 2000 box to the
> 2005 box. This will allow us to do queries on each, test the data and
> security settings are the same, and then *instantly* transfer the
> application to pull from the 2005 box when testing is complete.
> 1) If the 2005's database starts as blank, will it copy over all existing
> data, or just the data for new inserts/updates/deletes?
> 2) How do I enable replication, and of what type, on each box? I have a
> book on the 2005 beta, which helps a little bit, but I'm still pretty lost
> on what to set up on both boxes.
> 3) Will I have to reboot the 2000 box anytime in this process? I can't
> do
> that. It's live 24/7.
> 4) What happens if the receiving box, the 2005 one, is rebooted? Will it
> catch up with that couple minutes of lost data when it is back online?
>
how to enable replication from 2000 to 2005
I have never done replication before, so treat me like a novice, even though
I'm otherwise familiar with SQL Server.
I have a database on a SQL 2000 machine. Soon, I want to port the database
to SQL 2005, but in the meantime, I want to do some testing against our new
2005 box. I thought I should enable replication from the 2000 box to the
2005 box. This will allow us to do queries on each, test the data and
security settings are the same, and then *instantly* transfer the
application to pull from the 2005 box when testing is complete.
1) If the 2005's database starts as blank, will it copy over all existing
data, or just the data for new inserts/updates/deletes?
2) How do I enable replication, and of what type, on each box? I have a
book on the 2005 beta, which helps a little bit, but I'm still pretty lost
on what to set up on both boxes.
3) Will I have to reboot the 2000 box anytime in this process? I can't do
that. It's live 24/7.
4) What happens if the receiving box, the 2005 one, is rebooted? Will it
catch up with that couple minutes of lost data when it is back online?1. The replication engine will generate a snapshot of the 2000 machine, data
and structure, and apply it to the 2005 machine. Changes will then be sent
from publisher to subscriber. You may need to manually transfer other
objects such as procedures, views, triggers, etc. You will have to transfer
logins and users yourself.
2. There is a replication wizard which can take you through the process.
You should be able to use transactional replication. You'll want to
configure the distributor on the 2005 machine.
3. No, it does not require a reboot.
4. If either the publisher or subscriber goes down, replication will pick up
where it left off. The amount of time to catch up is dependent upon the
volume of data needing to be sent and the bandwidth available to send it.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"HK" <replywithingroup@.notreal.com> wrote in message
news:vMOIf.8366$Jg.7375@.tornado.socal.rr.com...
>I have never done replication before, so treat me like a novice, even
>though
> I'm otherwise familiar with SQL Server.
> I have a database on a SQL 2000 machine. Soon, I want to port the
> database
> to SQL 2005, but in the meantime, I want to do some testing against our
> new
> 2005 box. I thought I should enable replication from the 2000 box to the
> 2005 box. This will allow us to do queries on each, test the data and
> security settings are the same, and then *instantly* transfer the
> application to pull from the 2005 box when testing is complete.
> 1) If the 2005's database starts as blank, will it copy over all existing
> data, or just the data for new inserts/updates/deletes?
> 2) How do I enable replication, and of what type, on each box? I have a
> book on the 2005 beta, which helps a little bit, but I'm still pretty lost
> on what to set up on both boxes.
> 3) Will I have to reboot the 2000 box anytime in this process? I can't
> do
> that. It's live 24/7.
> 4) What happens if the receiving box, the 2005 one, is rebooted? Will it
> catch up with that couple minutes of lost data when it is back online?
>sql
I'm otherwise familiar with SQL Server.
I have a database on a SQL 2000 machine. Soon, I want to port the database
to SQL 2005, but in the meantime, I want to do some testing against our new
2005 box. I thought I should enable replication from the 2000 box to the
2005 box. This will allow us to do queries on each, test the data and
security settings are the same, and then *instantly* transfer the
application to pull from the 2005 box when testing is complete.
1) If the 2005's database starts as blank, will it copy over all existing
data, or just the data for new inserts/updates/deletes?
2) How do I enable replication, and of what type, on each box? I have a
book on the 2005 beta, which helps a little bit, but I'm still pretty lost
on what to set up on both boxes.
3) Will I have to reboot the 2000 box anytime in this process? I can't do
that. It's live 24/7.
4) What happens if the receiving box, the 2005 one, is rebooted? Will it
catch up with that couple minutes of lost data when it is back online?1. The replication engine will generate a snapshot of the 2000 machine, data
and structure, and apply it to the 2005 machine. Changes will then be sent
from publisher to subscriber. You may need to manually transfer other
objects such as procedures, views, triggers, etc. You will have to transfer
logins and users yourself.
2. There is a replication wizard which can take you through the process.
You should be able to use transactional replication. You'll want to
configure the distributor on the 2005 machine.
3. No, it does not require a reboot.
4. If either the publisher or subscriber goes down, replication will pick up
where it left off. The amount of time to catch up is dependent upon the
volume of data needing to be sent and the bandwidth available to send it.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"HK" <replywithingroup@.notreal.com> wrote in message
news:vMOIf.8366$Jg.7375@.tornado.socal.rr.com...
>I have never done replication before, so treat me like a novice, even
>though
> I'm otherwise familiar with SQL Server.
> I have a database on a SQL 2000 machine. Soon, I want to port the
> database
> to SQL 2005, but in the meantime, I want to do some testing against our
> new
> 2005 box. I thought I should enable replication from the 2000 box to the
> 2005 box. This will allow us to do queries on each, test the data and
> security settings are the same, and then *instantly* transfer the
> application to pull from the 2005 box when testing is complete.
> 1) If the 2005's database starts as blank, will it copy over all existing
> data, or just the data for new inserts/updates/deletes?
> 2) How do I enable replication, and of what type, on each box? I have a
> book on the 2005 beta, which helps a little bit, but I'm still pretty lost
> on what to set up on both boxes.
> 3) Will I have to reboot the 2000 box anytime in this process? I can't
> do
> that. It's live 24/7.
> 4) What happens if the receiving box, the 2005 one, is rebooted? Will it
> catch up with that couple minutes of lost data when it is back online?
>sql
Monday, March 12, 2012
How to duplicate table structure in Transactional replication?
Dear all:
After I create a new publication and its subscription by Transactional
replication in SQL server 2000,I want to add a column or alter a column
length in publication table and hope that the column can be duplicated to
subscription table.However,I find that Transactional replication in SQL
server 2000 can only replicate data and can not replicate table structure.
The replication type I use is "Transactional replication".
My problem is:
How to duplicate table structure in Transactional replication of SQL server
2000?
On 8 Jun, 04:45, gzwangyang <gzwangy...@.discussions.microsoft.com>
wrote:
> Dear all:
> After I create a new publication and its subscription by Transactional
> replication in SQL server 2000,I want to add a column or alter a column
> length in publication table and hope that the column can be duplicated to
> subscription table.However,I find that Transactional replication in SQL
> server 2000 can only replicate data and can not replicate table structure.
> The replication type I use is "Transactional replication".
> My problem is:
> How to duplicate table structure in Transactional replication of SQL server
> 2000?
What you're trying to do isn't strictly possible. You can't alter a
table that is published for replication.
You would need to drop replication, change the table and then re-
enable the replication with snapshot enabled. Provided your articles
snapshot attributes are correct it will create the table at the
subscriber.
Thanks
James
|||This is not correct. You can use sp_repladdcolumn and sp_repldropcolumn.
Altering a column is not straightforward but is achievable
(http://www.replicationanswers.com/AddColumn.asp).
Cheers,
Paul Ibison
After I create a new publication and its subscription by Transactional
replication in SQL server 2000,I want to add a column or alter a column
length in publication table and hope that the column can be duplicated to
subscription table.However,I find that Transactional replication in SQL
server 2000 can only replicate data and can not replicate table structure.
The replication type I use is "Transactional replication".
My problem is:
How to duplicate table structure in Transactional replication of SQL server
2000?
On 8 Jun, 04:45, gzwangyang <gzwangy...@.discussions.microsoft.com>
wrote:
> Dear all:
> After I create a new publication and its subscription by Transactional
> replication in SQL server 2000,I want to add a column or alter a column
> length in publication table and hope that the column can be duplicated to
> subscription table.However,I find that Transactional replication in SQL
> server 2000 can only replicate data and can not replicate table structure.
> The replication type I use is "Transactional replication".
> My problem is:
> How to duplicate table structure in Transactional replication of SQL server
> 2000?
What you're trying to do isn't strictly possible. You can't alter a
table that is published for replication.
You would need to drop replication, change the table and then re-
enable the replication with snapshot enabled. Provided your articles
snapshot attributes are correct it will create the table at the
subscriber.
Thanks
James
|||This is not correct. You can use sp_repladdcolumn and sp_repldropcolumn.
Altering a column is not straightforward but is achievable
(http://www.replicationanswers.com/AddColumn.asp).
Cheers,
Paul Ibison
How to drop merge replication system tables
Hi, we have a database wich used merge replication.
We disabled merge on this db, but '%onflict%' system tables persists,
leading to error when trying to drop them.
How can I drop those tables?
TIA,
Roberto Souza.
You could use sp_subscription_cleanup
There's a fairly good list of sp's used in replication at this site:
http://doc.ddart.net/mssql/sql70/sp_00.htm
"Roberto Souza" wrote:
> Hi, we have a database wich used merge replication.
> We disabled merge on this db, but '%onflict%' system tables persists,
> leading to error when trying to drop them.
> How can I drop those tables?
> TIA,
> Roberto Souza.
>
>
|||AFAIR this won't remove them. You should be able to use
drop table and the tablename from Query Analyser though.
Rgds,
Paul Ibison
We disabled merge on this db, but '%onflict%' system tables persists,
leading to error when trying to drop them.
How can I drop those tables?
TIA,
Roberto Souza.
You could use sp_subscription_cleanup
There's a fairly good list of sp's used in replication at this site:
http://doc.ddart.net/mssql/sql70/sp_00.htm
"Roberto Souza" wrote:
> Hi, we have a database wich used merge replication.
> We disabled merge on this db, but '%onflict%' system tables persists,
> leading to error when trying to drop them.
> How can I drop those tables?
> TIA,
> Roberto Souza.
>
>
|||AFAIR this won't remove them. You should be able to use
drop table and the tablename from Query Analyser though.
Rgds,
Paul Ibison
Friday, March 9, 2012
How to drop a database in loading / suspect mode
I tryed a "point in time restore" of a database which is used for replication
into a new database. This restore failed and the database is now in loading /
suspect mode. How can I delete this database.
When I try to drop the database e.g. in enterprise manager I get Error 3724
(used for replication). To stop the replication isn't possible either because
the "restore is in process".
Thanks for your help
UrsFunny enough I had this problem the other day.
I solved it by cancelling the process that was doing the
restore, then detaching and re-attaching the database.
Worked fine after that.
(NB my replication had stopped)
Peter
"Cauliflower is nothing but cabbage with a college
education."
Mark Twain
>--Original Message--
>I tryed a "point in time restore" of a database which is
used for replication
>into a new database. This restore failed and the database
is now in loading /
>suspect mode. How can I delete this database.
>When I try to drop the database e.g. in enterprise
manager I get Error 3724
>(used for replication). To stop the replication isn't
possible either because
>the "restore is in process".
>Thanks for your help
>Urs
>.
>
into a new database. This restore failed and the database is now in loading /
suspect mode. How can I delete this database.
When I try to drop the database e.g. in enterprise manager I get Error 3724
(used for replication). To stop the replication isn't possible either because
the "restore is in process".
Thanks for your help
UrsFunny enough I had this problem the other day.
I solved it by cancelling the process that was doing the
restore, then detaching and re-attaching the database.
Worked fine after that.
(NB my replication had stopped)
Peter
"Cauliflower is nothing but cabbage with a college
education."
Mark Twain
>--Original Message--
>I tryed a "point in time restore" of a database which is
used for replication
>into a new database. This restore failed and the database
is now in loading /
>suspect mode. How can I delete this database.
>When I try to drop the database e.g. in enterprise
manager I get Error 3724
>(used for replication). To stop the replication isn't
possible either because
>the "restore is in process".
>Thanks for your help
>Urs
>.
>
Friday, February 24, 2012
How to do SharePoint Site Replication?
How can I replicate SharePoint Site to other SharePoint Site?
Does SharePoint Portal Services support replication between two sites?
Any help is much appreciated. Thanks
According to MS support, SQL replication is not supported by
Sharepoint"
I tried to replicate data in the content database using transactional
replication and editors of sharepoint sites got errors when trying to
upload files to sharepoint sites.
On Wed, 26 Oct 2005 13:06:05 -0700, =?Utf-8?B?SGFzaGVy?=
<Hasher@.discussions.microsoft.com> wrote:
>How can I replicate SharePoint Site to other SharePoint Site?
>Does SharePoint Portal Services support replication between two sites?
>Any help is much appreciated. Thanks
Does SharePoint Portal Services support replication between two sites?
Any help is much appreciated. Thanks
According to MS support, SQL replication is not supported by
Sharepoint"
I tried to replicate data in the content database using transactional
replication and editors of sharepoint sites got errors when trying to
upload files to sharepoint sites.
On Wed, 26 Oct 2005 13:06:05 -0700, =?Utf-8?B?SGFzaGVy?=
<Hasher@.discussions.microsoft.com> wrote:
>How can I replicate SharePoint Site to other SharePoint Site?
>Does SharePoint Portal Services support replication between two sites?
>Any help is much appreciated. Thanks
How to do Replication in SQL Server 2005
Hi,
I have two servers with sql server 2005, one is in the main office and the other in a store...
I would like that the items table from the main office send new data to the server at store, and the sales data from the store to be send to the main office, can anyone help me to do that?!
Thanks
moved to replication forum
|||There are three type of replications in SQL Server
(a) Snapshot
(b) Transactional
(b) Merge
What i feel is you can configure Trasactional replication.
There are many documentation available in net. pse have a look on this
http://blog.csdn.net/longrujun/archive/2006/06/09/783357.aspx
Madhu
how to do replication from access 2000 to sql server 2000
My requirement i want to create publisher in access 2000 and subscribe the
data from sql server by using pull replication
Thanks in advance for any reply
Try creating a merge publication in sql server and set up the access
database as a heterogenous subscriber.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
data from sql server by using pull replication
Thanks in advance for any reply
Try creating a merge publication in sql server and set up the access
database as a heterogenous subscriber.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Subscribe to:
Posts (Atom)