Is there any advantages of using views in the same DB instead of tables in a differen

I've two databases. PROD & ARCHIVE
I need to archive data from production to archive database.
Right now I am using stored procedures to move from prod to archive.
If I use views in PROD which will reflect the ARCHIVE database tables, Is
there any advantages on connection?
Is "insert ...from archive.dbo.tableA select ....from prod.dbo.tableA" is
having connection over head over the views?
Please advice...Thanks...ShafNo overhead. The views would be only for typing convenience. If on 2005, syn
onyms would probably be
better if you just don't want to type in the database name.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Shaf.Khalidh" <itsprobablyme@.msn.com> wrote in message
news:uVclgt$GGHA.2440@.TK2MSFTNGP14.phx.gbl...
> I've two databases. PROD & ARCHIVE
> I need to archive data from production to archive database.
> Right now I am using stored procedures to move from prod to archive.
> If I use views in PROD which will reflect the ARCHIVE database tables, Is
there any advantages on
> connection?
> Is "insert ...from archive.dbo.tableA select ....from prod.dbo.tableA" i
s having connection over
> head over the views?
> Please advice...Thanks...Shaf
>|||Thanks Tibor,
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23AvomFAHGHA.240@.TK2MSFTNGP11.phx.gbl...
> No overhead. The views would be only for typing convenience. If on 2005,
> synonyms would probably be better if you just don't want to type in the
> database name.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Shaf.Khalidh" <itsprobablyme@.msn.com> wrote in message
> news:uVclgt$GGHA.2440@.TK2MSFTNGP14.phx.gbl...
>