all groups > sql server replication > may 2004 >
You're in the

sql server replication

group:

Replication vs Log Shipping vs 3rd Party


Replication vs Log Shipping vs 3rd Party WillCWirtz NO[at]SPAM Yahoo.com
5/7/2004 9:26:00 AM
sql server replication:
my company is running SQL Server 2000 ENT for its Axapta
implementation. we would like to create a reporting server to
off-load some of the resource intensive reports. Our original thought
was Replication, but Axapta does not have primary keys on thier tables
so Replication will not work. Then we thought of Log Shipping, but
management wants the data to be realtime (Log Ship every minute). I
don't know if log shipping is suited for this or if it is even
feasible to log ship every minute for a database that is already
working hard on transactional data.

Does anyone know what our best option is? Is there a third party tool
that would be better suited for this functionality? Can Log Shipping
Re: Replication vs Log Shipping vs 3rd Party Paul Ibison
5/7/2004 8:11:19 PM
Will,
as you say, log shipping works at the most frequently once per minute.
The obligation to have a primary key in replication which you refer to is
related to transactional replication. Snapshot and merge have no such
restriction. In fact, I would suggest investigating merge for your
requirements, which can have a much reduced latency.
Regards,
Paul Ibison

Re: Replication vs Log Shipping vs 3rd Party Will Wirtz
5/7/2004 11:01:03 PM


I completely agree that Log Shipping just is not practical for a real
time solution. Also, I don't think that I can use transactional
replication because most of the Axapta tables don't have primary keys
and adding keys to that many tables is not really an option. Not to
mention the possible effect it could have on the performance. So my
last thought was merge replication. But in walking through an example I
find out that it will automatically generate primary keys for tables
that don't have them. It then displays some warning like INSERT
statements that don't specify column names will fail. Not good. I
think I would have a dozen or so developers hunting me down and
management would be providing me with my very own cardboard box. : )

If any of my findings are wrong please let me know. I'm willing to try
just about anything.

Thanks.

*** Sent via Developersdex http://www.developersdex.com ***
Re: Replication vs Log Shipping vs 3rd Party Hilary Cotter
5/7/2004 11:32:47 PM
I don't advise using log shipping to provide real time replication.

Dumping your tlog every minute, although possible, is not practical as your
SQL Server will be continually dumping the log causing a performance impact.

You would be better off using transactional or merge replication.

As you don't have any primary keys on your tables you should think about
either changing your tables into views, and putting pk's on the underlying
tables or using merge replication.

[quoted text, click to view]

Re: Replication vs Log Shipping vs 3rd Party Hilary Cotter
5/8/2004 10:23:00 AM
the type of insert statement that will fail with the GUID column is an
unqualified insert ie

insert into table1
select * from table2

where table 1 does not have an added guid column and table2 does.

You can solve this problem by adding a guid column to table1 as well, which
sometimes works, or to recreate your tables as views and have the new
underlying tables having PK's.

Most tables in a relational database by definition should have PK's. If they
don't it is highly possible that you will be running into other errors due
to the overall poor database design.

[quoted text, click to view]

Re: Replication vs Log Shipping vs 3rd Party Will Wirtz
5/8/2004 8:17:19 PM
Hilary,

The database I'm refering to is an Microsoft Axapta database. It's my
companies ERP package and contains hundreds and hundreds of tables. I
am told that primary keys were not used in most tables for performance
reasons. And because it was a purchased package, I don't know how most
of the SQL Insert statements were written and I can't really allow Merge
Replication to just starting adding columns. It sounds like I'm running
out of options.

Do you know of any other software packages that can provide somewhat
real-time database replictation to a read-only server?



*** Sent via Developersdex http://www.developersdex.com ***
Re: Replication vs Log Shipping vs 3rd Party Hilary Cotter
5/9/2004 5:18:34 PM
I've worked with a few, the only one I might recommend is Data Mirror, but
it also required PK's for replicating from SQL Server.

--
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html


[quoted text, click to view]

Re: Replication vs Log Shipping vs 3rd Party Dean
5/10/2004 1:19:09 PM
Sounds a little like PeopleSoft. All tables have Clustered unique indexes
but no Keys. Could you turn these indexes into Keys?


[quoted text, click to view]

Re: Replication vs Log Shipping vs 3rd Party Hilary Cotter
5/11/2004 6:36:04 AM
unique indexes are just like primary keys, although a unique index will
accept a single null where pk's don't. I have been able to convert unique
indexes into pk's.


--
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html


[quoted text, click to view]

AddThis Social Bookmark Button