I know that the view is the obvious way. What I'm not telling you is
that this data actually needs to reside in tables in Database B. The
going to be input manually and some is coming from Database A. So it
has to be in the tables, not a view. The application that is being
Andrew La Grange wrote:
> Hey.
>
> If it is always going to be on the same database server you could just
> create a view on Database B, that pulls from the view on Database A; in
> which case it would be realtime and there would be no need for
> replication or DTS (which would be overkill for this situation).
>
> Would look something like this:
>
> CREATE VIEW [DatabaseB].[dbo].[vDestinationView]
> AS
> SELECT * FROM [DatabaseA].[dbo].[vSourceView]
> GO
>
> Other quick and easy ways to go would be an IF NOT EXISTS INSERT INTO
> job running on the SQL Agent as often as you need the data moved over,
> but that is a bit nasty.
>
> Hope this helps.
>
> Andrew la Grange
> -------------------------------------
> BUSINESS ARTISTS
> Systems / Solutions / Consulting
> Web:
http://www.businessartists.co.za > -------------------------------------
>
>
>
> mkerrigan@ktoys.com wrote:
> > I have two databases on the same server. I want to populate and keep
> > synchronized a table on database 2 from a view on database 1. Whenever
> > data would change in the underlying tables on database 1, it would
> > update the table on database 2. Is this something that can be done
> > through replication or should I use a DTS? Thing is, we want it to be
> > as close to real-time as possible. I know what I'm trying to do
> > doesn't seem to make much sense, but it's too long to get into here. I
> > just need an answer to the underlying problem, thanks!