Replication Options

Hi,
Sorry if this is too simple a question, but this is what happens when a developer does an admin job!
What options are available if we wanted to "replicate" a database to some off-site locations (lets say, 10 locations).
The replication would be weekly. Its possible that some of the sites will not have direct access to the publishing site.
Many thanks in advance for any help.
Andy
Andy,
I'd need more info to decide the relevant suggestion for your particular
situation. For instance, can the schema on the publisher be changed by
adding another column (with a default), does the schema on the publisher and
subscriber need to be identical, do the subscribers need to be able to
change the data. If subscribers will be changing the data, can the
subscribers potentially change the same data.
Cheers,
Paul Ibison
|||Paul,
The schema on the publisher could potentially change, though not very often - only if we change the db for a specific requirement.
Luckily, the users will not be able to change the data - we only want to replicate business standing data, which can only be changed centrally, and should replicate to all our other sites.
I hope this helps.
TIA
Andy
"Paul Ibison" wrote:

> Andy,
> I'd need more info to decide the relevant suggestion for your particular
> situation. For instance, can the schema on the publisher be changed by
> adding another column (with a default), does the schema on the publisher and
> subscriber need to be identical, do the subscribers need to be able to
> change the data. If subscribers will be changing the data, can the
> subscribers potentially change the same data.
> Cheers,
> Paul Ibison
>
>
|||p.s. I'm looking for a best practice of the situation. If SQL Server Replication isn't the best way, please let me know - I've been looking into log shipping etc too, but have yet to find an answer... Maybe the answer is simply to email round csv files a
nd upload these monthly?
"Paul Ibison" wrote:

> Andy,
> I'd need more info to decide the relevant suggestion for your particular
> situation. For instance, can the schema on the publisher be changed by
> adding another column (with a default), does the schema on the publisher and
> subscriber need to be identical, do the subscribers need to be able to
> change the data. If subscribers will be changing the data, can the
> subscribers potentially change the same data.
> Cheers,
> Paul Ibison
>
>
|||Andy,
this article may help you decide:
http://www.sqlservercentral.com/colu...eplication.asp
In addition, if the schema will change, then adding columns and deleting
columns can in most cases be handled by replication. Altering an existing
column or dropping an article may result in the need for reinitialization
(depends on replication type and what column change is needed).
HTH,
Paul Ibison

Replication of DB2 data on SQL Server

What tools are available to update SQL Server application tables from a DB2 database?
The DB2 database is on iSeries (AS/400).
Thanks in advance.you can probably create a linked server from SQL Server to DB2 and then use select statements as usual. search for db2 on the link below.

http://msdn2.microsoft.com/en-us/library/ms190479.aspx|||It really depends on the version of SQL Server you are running. Linked servers as mentioned is one option, another option is using DTS or SSIS to transfer data regulary. Unfortunately it appears that you have to pull the data from the SQL Server, I don't think the AS/400 will be able to push data to the SQL Server.|||You could write java programs to push data either way using an JDBC connectivity.

We can also look @. tools from IBM to push data to SQL Server using DB2 Information Integrator V8, IBM DB2 Replication & DataPropagator.