Multi location data syncronization

We have a scenario that will require us to maintain a central system that
will be taking in data from 15 other locations around the state. I'm
interested in creating a situation that will allow the individual locations
the ability to have a local copy of their data, but only their data. We want
changes made to the central repository to be pushed back down the the
appropriate location. It there a way or doing this through some kind of SQL
Server transaction synchronization? Could we have each locations data use
SQL Server log/transaction shipping synchronizing into individual databases
at the central site and then have some process that would just merge each of
these databases into a single large database? Is this more of a headache to
try to create and maintain? Any ideas or suggestions would be great. The
main idea here is that each location is a separate entity collecting their
own data - we are acting as a repository for all the locations and want to
be able to do research analysis on the data as a whole. As I said, any ideas
or suggestions would be welcome! Thanks!
>
> We have a scenario that will require us to maintain a central system
that
> will be taking in data from 15 other locations around the state. I'm
> interested in creating a situation that will allow the individual
locations
> the ability to have a local copy of their data, but only their data. We
want
> changes made to the central repository to be pushed back down the the
> appropriate location. It there a way or doing this through some kind of
SQL
> Server transaction synchronization? Could we have each locations data use
> SQL Server log/transaction shipping synchronizing into individual
databases
> at the central site and then have some process that would just merge each
of
> these databases into a single large database? Is this more of a headache
to
> try to create and maintain? Any ideas or suggestions would be great. The
> main idea here is that each location is a separate entity collecting
their
> own data - we are acting as a repository for all the locations and want
to
> be able to do research analysis on the data as a whole. As I said, any
ideas
> or suggestions would be welcome! Thanks!
It looks your requirement conforms to the multiple publishers and central
subscriber physical model. For more info, please consult SQL Server Books
Online.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Multi location data syncronization

We have a scenario that will require us to maintain a central system that
will be taking in data from 15 other locations around the state. I'm
interested in creating a situation that will allow the individual locations
the ability to have a local copy of their data, but only their data. We want
changes made to the central repository to be pushed back down the the
appropriate location. It there a way or doing this through some kind of SQL
Server transaction synchronization? Could we have each locations data use
SQL Server log/transaction shipping synchronizing into individual databases
at the central site and then have some process that would just merge each of
these databases into a single large database? Is this more of a headache to
try to create and maintain? Any ideas or suggestions would be great. The
main idea here is that each location is a separate entity collecting their
own data - we are acting as a repository for all the locations and want to
be able to do research analysis on the data as a whole. As I said, any ideas
or suggestions would be welcome! Thanks!>
> We have a scenario that will require us to maintain a central system
that
> will be taking in data from 15 other locations around the state. I'm
> interested in creating a situation that will allow the individual
locations
> the ability to have a local copy of their data, but only their data. We
want
> changes made to the central repository to be pushed back down the the
> appropriate location. It there a way or doing this through some kind of
SQL
> Server transaction synchronization? Could we have each locations data use
> SQL Server log/transaction shipping synchronizing into individual
databases
> at the central site and then have some process that would just merge each
of
> these databases into a single large database? Is this more of a headache
to
> try to create and maintain? Any ideas or suggestions would be great. The
> main idea here is that each location is a separate entity collecting
their
> own data - we are acting as a repository for all the locations and want
to
> be able to do research analysis on the data as a whole. As I said, any
ideas
> or suggestions would be welcome! Thanks!
--
It looks your requirement conforms to the multiple publishers and central
subscriber physical model. For more info, please consult SQL Server Books
Online.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Multi location data syncronization

We have a scenario that will require us to maintain a central system that
will be taking in data from 15 other locations around the state. I'm
interested in creating a situation that will allow the individual locations
the ability to have a local copy of their data, but only their data. We want
changes made to the central repository to be pushed back down the the
appropriate location. It there a way or doing this through some kind of SQL
Server transaction synchronization? Could we have each locations data use
SQL Server log/transaction shipping synchronizing into individual databases
at the central site and then have some process that would just merge each of
these databases into a single large database? Is this more of a headache to
try to create and maintain? Any ideas or suggestions would be great. The
main idea here is that each location is a separate entity collecting their
own data - we are acting as a repository for all the locations and want to
be able to do research analysis on the data as a whole. As I said, any ideas
or suggestions would be welcome! Thanks!>
> We have a scenario that will require us to maintain a central system
that
> will be taking in data from 15 other locations around the state. I'm
> interested in creating a situation that will allow the individual
locations
> the ability to have a local copy of their data, but only their data. We
want
> changes made to the central repository to be pushed back down the the
> appropriate location. It there a way or doing this through some kind of
SQL
> Server transaction synchronization? Could we have each locations data use
> SQL Server log/transaction shipping synchronizing into individual
databases
> at the central site and then have some process that would just merge each
of
> these databases into a single large database? Is this more of a headache
to
> try to create and maintain? Any ideas or suggestions would be great. The
> main idea here is that each location is a separate entity collecting
their
> own data - we are acting as a repository for all the locations and want
to
> be able to do research analysis on the data as a whole. As I said, any
ideas
> or suggestions would be welcome! Thanks!
--
It looks your requirement conforms to the multiple publishers and central
subscriber physical model. For more info, please consult SQL Server Books
Online.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

MSSQL Version

I have currently Standard Edition of MSSQL installed on my various servers. These servers are interacting with my one central server which also has Standard Edition of MSSQL.
Please let me know if I change my central server Standard Edition of MSSQL to Enterprise Edition and keep the other server with the Standard Edition, will this effect the working ?
Also please confirm, what are the changes in terms of query syntax or database setting that I will have to change for this change of version.i would not imagine there'd be any change required in your sql code as it remains fairly standard.

if you change the central server to enterprise edition you will obviously have to do some reconfigurations, but that's a given when installing something new, but i wouldn't imagine anything too drastic.

should connect and run well, good luck|||You can run a mix of Developer, Personal, Standard, and Enterprise versions of SQL Server with no problem. The Transact-SQL syntax is exactly the same on all of them, although there may be some SQL features that only exist on certain versions. As an example, clustering is only available to the Enterprise version, so you can't use clustering features in the Standard version, although the syntax would be the same if you could.

-PatP|||Thanks a lot !