Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
likwid
Starting Member
3 Posts |
 Posted - 2002-03-28 : 18:02:02
|
| I recently was asked to evaluate some existing database designs. 1 issue I saw was a stored procedure calling another database on the same server for a lookup. This seems a little kludgy to me. Can anyone explain why exactly this is a bad idea. (If indeed it is.) I am also looking for some information like a url or document that supports this. Thanks,./Likwid |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2002-03-28 : 19:37:58
|
| The only reason I can think that this would be "kludgy" would be if that second database only existed to do lookups for the first database. Then the question would be, "Why isn't it just included in the first database?" But, if the second database exists because it has a use of its own, and the only connection to the first one is for this lookup, then I don't see this as a bad thing.------------------------GENERAL-ly speaking... |
 |
|
|
JohnDeere
Posting Yak Master
191 Posts |
Posted - 2002-03-29 : 00:10:03
|
| I don't know if this classifies as kludgy but the names of the databases are hard coded into the procedures that do the cross database queries. This can be a gotcha if your development and production are not named the same. Every time you deploy you have to change the names in the procedures.LHarra"They that can give up essential liberty to obtain a little temporary safetydeserve neither liberty nor safety."(Benjamin Franklin) |
|
|
|
|
|
|
CROSS DB QUERIES