|
|
You're in the
sql server replication
group:Best Replication Method to Use
sql server replication:
We want to allow our customer base to be able to access their account
information online. I want to setup a second SQL server so the customers can use this for looks up. The front end to access this info is web based. What replication method is the best one to use to update the database say
I think transactional replication would work for this. However this will
require each table you are replicating to have a primary key. I am a little confused by the data flow. Are you saying data moves from the web server SQL Server database to another SQL Server? Or is it moving internally to the SQL Server supporting the web site. -- 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 [quoted text, click to view] "Scopus69" <Scopus69@nospam.postalias> wrote in message news:3D5CC7EA-4702-417E-AE2D-9985B1E4B781@microsoft.com... > We want to allow our customer base to be able to access their account > information online. I want to setup a second SQL server so the customers > can > use this for looks up. The front end to access this info is web based. > > What replication method is the best one to use to update the database say > every 24 hours at night? Thanks!!
Sorry for the confusion. The GUI interface to the data is a web interface
that connects to the backend SQL server. What I would like to do is setup another web & SQL server for our cutomers so they can use it for lookups. I really don't want them in our prduction DB. I was wondering what is the best way to get the data off the production SQL server to the customer SQL server on a nightly basis? I don't think log shipping will work because it will put the shipped DB in "read only" So what method would be the best to use? Thanks! [quoted text, click to view] "Hilary Cotter" wrote:
> I think transactional replication would work for this. However this will > require each table you are replicating to have a primary key. > > I am a little confused by the data flow. Are you saying data moves from the > web server SQL Server database to another SQL Server? Or is it moving > internally to the SQL Server supporting the web site. > > -- > 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 > > "Scopus69" <Scopus69@nospam.postalias> wrote in message > news:3D5CC7EA-4702-417E-AE2D-9985B1E4B781@microsoft.com... > > We want to allow our customer base to be able to access their account > > information online. I want to setup a second SQL server so the customers > > can > > use this for looks up. The front end to access this info is web based. > > > > What replication method is the best one to use to update the database say > > every 24 hours at night? Thanks!! > >
if your database is not too large, a snapshot replication maybe best for
you. else somekind of logshipping will be good too, see the other thread on simple log shipping. justin [quoted text, click to view] Scopus69 wrote:
> We want to allow our customer base to be able to access their account > information online. I want to setup a second SQL server so the customers can > use this for looks up. The front end to access this info is web based. > > What replication method is the best one to use to update the database say
I think transactional is your best bet.
-- 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 [quoted text, click to view] "Scopus69" <Scopus69@nospam.postalias> wrote in message news:76F950CE-B1EA-493F-8092-5ED6AA73EC75@microsoft.com... > Sorry for the confusion. The GUI interface to the data is a web interface > that connects to the backend SQL server. What I would like to do is > setup > another web & SQL server for our cutomers so they can use it for lookups. > I > really don't want them in our prduction DB. > > I was wondering what is the best way to get the data off the production > SQL > server to the customer SQL server on a nightly basis? I don't think log > shipping will work because it will put the shipped DB in "read only" > > So what method would be the best to use? Thanks! > > "Hilary Cotter" wrote: > >> I think transactional replication would work for this. However this will >> require each table you are replicating to have a primary key. >> >> I am a little confused by the data flow. Are you saying data moves from >> the >> web server SQL Server database to another SQL Server? Or is it moving >> internally to the SQL Server supporting the web site. >> >> -- >> 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 >> >> "Scopus69" <Scopus69@nospam.postalias> wrote in message >> news:3D5CC7EA-4702-417E-AE2D-9985B1E4B781@microsoft.com... >> > We want to allow our customer base to be able to access their account >> > information online. I want to setup a second SQL server so the >> > customers >> > can >> > use this for looks up. The front end to access this info is web based. >> > >> > What replication method is the best one to use to update the database >> > say >> > every 24 hours at night? Thanks!! >> >> >>
I also like Transactional Replication if the data is dynamic at the source
and the users who will be talking to your target server need updated information as well for their lookups. If current data is not an issue, that is they don't mind the data being static, then may be snapshot will work. But then again it depends on how large the data is. For me one way Transactional seems to fit the bill here. [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:enpFYKCDGHA.1028@TK2MSFTNGP11.phx.gbl... > I think transactional is your best bet. > > -- > 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 > > "Scopus69" <Scopus69@nospam.postalias> wrote in message > news:76F950CE-B1EA-493F-8092-5ED6AA73EC75@microsoft.com... > > Sorry for the confusion. The GUI interface to the data is a web interface > > that connects to the backend SQL server. What I would like to do is > > setup > > another web & SQL server for our cutomers so they can use it for lookups. > > I > > really don't want them in our prduction DB. > > > > I was wondering what is the best way to get the data off the production > > SQL > > server to the customer SQL server on a nightly basis? I don't think log > > shipping will work because it will put the shipped DB in "read only" > > > > So what method would be the best to use? Thanks! > > > > "Hilary Cotter" wrote: > > > >> I think transactional replication would work for this. However this will > >> require each table you are replicating to have a primary key. > >> > >> I am a little confused by the data flow. Are you saying data moves from > >> the > >> web server SQL Server database to another SQL Server? Or is it moving > >> internally to the SQL Server supporting the web site. > >> > >> -- > >> 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 > >> > >> "Scopus69" <Scopus69@nospam.postalias> wrote in message > >> news:3D5CC7EA-4702-417E-AE2D-9985B1E4B781@microsoft.com... > >> > We want to allow our customer base to be able to access their account > >> > information online. I want to setup a second SQL server so the > >> > customers > >> > can > >> > use this for looks up. The front end to access this info is web based. > >> > > >> > What replication method is the best one to use to update the database > >> > say > >> > every 24 hours at night? Thanks!! > >> > >> > >> > >
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |