Two issues come to my mind, if I'd be there I'd ask you:
1. Replication is an important thing in every database and so in WEB
databases too. You wouldn't want to update your main or production
database with your new information, so you'll do it on a secondary
database with the very same structure and use probably transactional
replication between the two. And here is the twist. Usually you protect
your very "end" environment behind a firewall. Now, here is the twist:
SQL Server requieres for a replication that every computer invloved
(primary/secondary or production/development, etc) were on the same
side of a firewall. Now we have a very handy software on our
development machine that can not get through a firewall, so we can not
move the firewall. How to raplicate? If we can not replicate how to
maintain the production database?
2. The secondary machine (for development) would have the purpose to
serve as a backup for the live primary system. (Though, the primary
system could have the RAID5 mirroring mirracle, but what if the whole
computer crashes?) As the secondary machine's DB is perfect copy of the
primary's, it consists some very denormalized tables in order to reduce
join widths (less tables possible) and enhence query performance.
So, it is hard to update a denormalized database (a client application
should fire lot of queries before doing anything) - rows relying on
rows in the same table, etc. Than you would need a third environment
with a DB optimized to maintain integrity in the data, with a more
fragmented and normalized structure, proper triggers, constraints,
keys, etc. Independently of the firewall story, it would be very
benefitial for those who want to implement a good data driven web site
to have some advice how to overcome this kind of situations: moving
consistent data from the third environment into the second environment
and back and forth automagicly and reliably? How to set up raplication,
what model to chose, or just use DTS.
Sorry Joe, it was not about XML track.
> I have to give a talk tomorrow in The Netherlands on web databases.
> This is not really my area of expertise, so I know I mised something.
> How about a litle help here? What topics are important? What should I
> say about them? etc. The conference has an XML track.
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Sent via Deja.com http://www.deja.com/
Before you buy.