Groups | Blog | Home
all groups > sql server clustering > march 2004 >

sql server clustering : Recommended Setup


Bon733
3/8/2004 8:56:08 PM
Bon733
3/9/2004 2:40:44 PM
Great. Thanks for the input.

Have you had any problems with the transactional replication adding the
timestamp column to your tables? I have had some bad experience because of
poorly written software using INSERT INTO ... SELECT * FROM ... so the
stored procedures or coding bombs out.



[quoted text, click to view]

Carlos Eduardo Rojas
3/9/2004 4:05:26 PM
We have an OLTP database here with heavy reporting activity, and what we do
is that we have transactional replication configured from the production
server to the reporting server. This also allows us to create different
indexes on the reporting server to optimize reporting queries.

--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example


[quoted text, click to view]
manufacturing environment (i.e. production runs, accounting). I would like
to get an idea as to the design that would allow us to run two servers with
SQL Server in order to produce the best response time. My goal is to have
one server for production and another server as a reporting server. Should I
set them up in a clustered environment (active/active), log shipping, or
replication? If anyone has some good technical srticles, please let me know.

Darren Green
3/10/2004 7:22:29 PM

In message <#Mlp#diBEHA.2804@tk2msftngp13.phx.gbl>, Bon733
<bon@nospam.com> writes
[quoted text, click to view]

Transactional replication does not require timestamps. It is only
one-way, so there is no requirement for the change detection that
timestamps offer. You're thinking of merge replication, when yes this
can be a pain.

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org
cgross NO[at]SPAM online.microsoft.com
3/11/2004 4:14:47 PM
If you choose the immediate updating or queued updating options for
transactional replication, then that will change your schema. If you don't
choose either of those options then you don't have column additions and
triggers.

If you're doing a lot of data manipulation as you move the data, you may
want to look into DTS. You can even use DTS as part of some types of
replication.

If you're going to do reporting, consider installing Analysis Services
and/or Reporting Services. Analysis Services is available on the same CD as
SQL Server, Reporting Services is a free add-on.

Having separate servers will help performance for both your production
(OLTP) system and your reporting (OLAP) system. Whether or not you use
clustering and/or log shipping depends on your disaster recovery needs.
Even with clustering and log shipping you need a strong, well-planned,
well-tested backup strategy.

Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
AddThis Social Bookmark Button