In reality would you not tend to only need to read the user data at login time and then cache whatever user data is required (in a persistant scope of some type) so that your example would become
select a.title, u.firstname, u.lastname from articles a WHERE a.insertby = #request.account_id# aside from that I'm sure some MSSQL experts will answer your question more specifically :-) On Fri, 19 Nov 2004 10:02:45 -0500, Scott Mulholland <[EMAIL PROTECTED]> wrote: > In theory is there any downside to joining cross database. I'm using > sql server and was considering having my user data in one database and > my content data in an other. In some cases I would need to do something > like this as an example: > > 2 databases (MS SQL Server for arguments sake): USERS and CONTENT > > datasource=CONTENT > select a.title, u.firstname, u.lastname > from articles a INNER JOIN USERS.dbo.accounts u > ON a.insertby = u.account_id > > Is there any performance hit or other reasons to avoid having them as > separate databases? > > Thanks, > Scott > > --- > [This E-mail scanned for viruses by Declude Virus] > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Gold Sponsor - CFHosting.net http://www.cfhosting.net Message: http://www.houseoffusion.com/lists.cfm/link=i:4:184869 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
