Reply to Re: Moving data for reporting

Your name:

Reply:


Posted by Simon Hayes on 07/08/05 20:36

"joshsackett" <joshsackett@gmail.com> wrote in message
news:1120842056.005884.32200@g44g2000cwa.googlegroups.com...
>I need the data to be current, as they are reporting databases. The
> most lag-time I can have is about 15 minutes.
>

Ah, well you didn't include that in your "only" requirements... :-) Probably
transactional replication is still the best option, given the time
constraint, and if you can manage the schema changes; you can replicate
adding and dropping columns, but whole tables may be more awkward.
Personally, I would be concerned if the schema is constantly changing, and
especially if it's changing during working hours, but I appreciate that this
may be out of your control. If you can implement schema changes only during
defined and planned maintenance windows, then you should be able to handle
the snapshots at the same time.

You might also want to post in microsoft.public.sqlserver.replication, given
that replication is quite a specialized area.

Simon

[Back to original message]


Удаленная работа для программистов  •  Как заработать на Google AdSense  •  England, UK  •  статьи на английском  •  PHP MySQL CMS Apache Oscommerce  •  Online Business Knowledge Base  •  DVD MP3 AVI MP4 players codecs conversion help
Home  •  Search  •  Site Map  •  Set as Homepage  •  Add to Favourites

Copyright © 2005-2006 Powered by Custom PHP Programming

Сайт изготовлен в Студии Валентина Петручека
изготовление и поддержка веб-сайтов, разработка программного обеспечения, поисковая оптимизация