I have 2 DBs. One contains a table. "DB1" & "DB2" DB2 can either reference D1.Table1 in it's stored procs etc, or it can choose to "override" that table and create that table inside itself (DB2.Table1) and use that in it's stored procs etc.
Other than a view, which would be horrendous in this case since the data is not going to be even close to being static, I was wondering if anyone knew of anything else I could use.
Or are views against a single table an "ok" thing now to do for a table with constantly changing data?
Basically I just need some sort of "pointer" object that when a stored proc calls it it points to the right table without the programmer having to change 100 store procs when it's decided the DB2 will override the table in DB1.
I was always told that Views "recompile" thier data everytime a row changes in a table they reference. So that you only want Views against tables with very static data.
Alternative to Views
Posted - 08/25/2010 : 12:20:05
