Options.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

We're trying to pull approximately 50 tables out of a database of
16,000. Unfortunatley none of them have primary keys, they are all
keyed by multiple fields (mostly effective dated).

Ideally we'ld like to see only changed or inserted records be loaded
into the subscriber. (Those would be processed for a DW).

I can't find a neat solution.

We can't use transactional replication because there are no primary
keys,

if we used Snapshot replication then (as far as I can tell) we'ld have
to go through every line to see if it needed to be processed.

Log shipping won't work because of the sheer size of the database and
the smidgen of it that we actually want.

We've toyed with adding a timestamp to every table to be pulled, but
that gets into update issues and all sorts of potential problems down
the road.

Any suggestion would be very much appreciated, before I go totally
grey!!!

Ches Weldishofer
Clear Channel Worldwide

.

Relevant Pages

  • Re: Log Shipping - dumb question
    ... I am not able to use transactional replication as many ... of the database tables do not have primary keys and I am unable to ... change the database schema. ... Paul Ibison SQL Server MVP,www.replicationanswers.com ...
    (microsoft.public.sqlserver.replication)
  • query for tables without PK
    ... I have a database that I want to use transactional replication on but several of the tables don't have primary keys - is there a quick query that I can run that will return a list of the tables without PK's? ...
    (microsoft.public.sqlserver.replication)
  • Re: interview questions
    ... the most important thing is that they understand database DESIGN. ... There is no such thing as multiple primary keys in a ... Should an Autonumber field be used as a Primary Key? ... Normalization is a methodology or process for removing as much redundant ...
    (microsoft.public.access.tablesdbdesign)
  • Re: What happened to my PKs????
    ... I only want my users to have the ability to run reports over this database, and I want this database in sync with my production database with as minimal latency as possible, that's why I chose Transactional Replication. ... I thought that setting the "Not For Replication" on identity columns caused the records to just be written from the Publisher to the Subscriber, that the identity column isn't incremented. ... As you want a reporting server then I'd seriously consider log shipping as it can have quite a low latency and Everything is transferred - inc permissions. ...
    (microsoft.public.sqlserver.replication)
  • Re: interview questions
    ... the most important thing is that they understand database DESIGN. ... There is no such thing as multiple primary keys in a ... Should an Autonumber field be used as a Primary Key? ... Normalization is a methodology or process for removing as much redundant ...
    (microsoft.public.access.tablesdbdesign)