Yeah, that's what im trying to figure out, the benefits of doing it this way. It is not for a central users database shared by applications so that benefit is lost. I just wanted to know if there was some best practice out there for this. Aside from having these 2 different types of data seperated for organization I can't find any benefit to having them be 2 databases.
-----Original Message----- From: Michael Traher [mailto:[EMAIL PROTECTED] Sent: Friday, November 19, 2004 11:22 AM To: CF-Talk Subject: Re: Database design question Well if you need multiple users data - again this sounds like the sort of data that could be read once and cached, but you know your application and how dynamic the data is... The real question is what benefits do you get from having the user data in a separate database, because it will undoubtably add complications of one sort or another. On Fri, 19 Nov 2004 10:38:27 -0500, Scott Mulholland <[EMAIL PROTECTED]> wrote: > Well some user data would be stored in session vars, like the > account_id and such, but my example was more along the lines of if you > wanted to pull a list of articles to display the article and name of > the person who inserted it, whereas I take your query to give me the > list of articles inserted by a specific user. Am I misinterpretting > it? > > > > -----Original Message----- > From: Michael Traher [mailto:[EMAIL PROTECTED] > Sent: Friday, November 19, 2004 10:21 AM > To: CF-Talk > Subject: Re: Database design question > > 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:184893 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
