Reply to thread

Message

<blockquote data-quote="gamejester" data-source="post: 150410" data-attributes="member: 50634">Having multiple MP clients and 1 TV engine server (that also holds all the tv series episodes) I am also looking for a solution here.My goals are:1. central source for database and episode imgaes/banners/etc...I think a properly indexed SQL db on the tv engine server could be a good option here, but for speed of loading images I would expect them to be pulled from a local disc and mirrored to each machine. If you could specify the location of the banners then that gives people the option to either store local (and mirror) for speed or store on a central server using UNC to save disk space.2. watched TV episodes. I would like this information stored in a seperate db or xml file with a configurable location. I could then have 3 of the clients maintain their own list of which shows have been watched and another 2 clients point to a shared UNC location (say kitchen and lounge) reflecting the same viewing.The size of my TV database makes some of the views unusable. The machines are all good cor2duo based, but when switching from All list to Recent takes a good few seconds. I suspect a properly indexed SQL instance would sort this out.</blockquote>

[QUOTE="gamejester, post: 150410, member: 50634"] Having multiple MP clients and 1 TV engine server (that also holds all the tv series episodes) I am also looking for a solution here. My goals are: 1. central source for database and episode imgaes/banners/etc... I think a properly indexed SQL db on the tv engine server could be a good option here, but for speed of loading images I would expect them to be pulled from a local disc and mirrored to each machine. If you could specify the location of the banners then that gives people the option to either store local (and mirror) for speed or store on a central server using UNC to save disk space. 2. watched TV episodes. I would like this information stored in a seperate db or xml file with a configurable location. I could then have 3 of the clients maintain their own list of which shows have been watched and another 2 clients point to a shared UNC location (say kitchen and lounge) reflecting the same viewing. The size of my TV database makes some of the views unusable. The machines are all good cor2duo based, but when switching from All list to Recent takes a good few seconds. I suspect a properly indexed SQL instance would sort this out. [/QUOTE]

Verification