Can you guys think of all the possible reason why you wouldn't want 2 databases to cross reference each other using -
database.dbo.tablename
I can see one reason...Developers are going to go gagas using database.dbo.tablename for cross database updates/inserts etc. This will mean that the databases cannot scale anymore. What else?Hi,
because you would have to create the user which access the object not only in one database but also in the other one.
<Ignore this part, because this is a bad practice>
You could enable cross database ownership chain and use a view/procedure from database A to Select the data from Database B, opening up a security hole to database B, because the security is only checked once on Database A if the two owners of the objects are both the same.
<Ignore this part, because this is a bad practice>
Thats the hardest part for me, maintaing the user in two databases (without enabling cross database ownership chain)
HTH, Jens K. Suessmeyer.
-
http://www.sqlserver2005.de
-|||
Security issues, additional keystrokes required to use four part names, etc.
I can also think of many equally valid reasons to separate data between different databases. Security issues, Backup/Restore Issues, etc.
Saving Developers 'keystrokes' is a trivial concern and should be ignored. Make the decision based upon 'real' organizational needs and requirements. With drag and drop, cut and paste, etc., too many keystrokes is totally bogus!
sql
No comments:
Post a Comment