Hi Emile,

On 15/3/07 08:39, "Emiliano Heyns" <emiliano.he...@gmail.com> wrote:

> On 3/15/07, Hugh Williams <hwilli...@openlinksw.com> wrote:
>>>>> [Hugh] Virtuoso has the same 2GB limit, although this can be changed it
>>>>> need be but would break backward compatibility.
>>> 
>>> Ouch, I'm going to hit that limit pretty soon. After the music server thing
>>> I was thinking about extending the existing Virtuoso CMS stuff, but since
>>> I'd also be hosting image galleries, the 2GB is not going to suffice. I
>>> might have to look into creating a udt that stores the actual content
>>> outside virtuoso. Not my preference, but appearantly the 2GB thing is not
>>> uncommon. 
>>> 
>>> [Hugh] Can you please elaborate more on the need to a limit larger than 2GB
>>> as I am sure if we know more about what you are seeking to achieve a means
>>> can be devised for doing this all within virtuoso ?
> From the POV of the media server and the CMS+gallery:
> 
> $ du -sh photos video mp3
> 4.5G    photos
> 15G     video
> 31G     mp3
> 
> And I'm just a light user. Sharepoint does some icky stuff with spreading data
> that logically belong to one table around several tables to get past the 2GB
> limit, and since SQL Server doesn't have distributed keys, there goes the
> simple declarative method of consistency control. You're very much not
> supposed to muck around in the SQL Server database hsoting your sharepoint for
> reasons like this. Which kind of defeats the purpose of using a DBMS as your
> storage facility.
> 
> I'll still look into the UDT that hosts large blobs outside the DB storage,
> but that does complicate ensuring data-metadata consistency.
> 
> [Hugh] I presume photos, video and mp3 are folders containing individual
> files, in which are any of the physical files within these folders greater
> than 2GB, as that is the only point at which Virtuoso would have a problem
> storing them ? If the files are less that 2GB in size then Virtuoso can
> efficiently manage such file stored in WebDAV storing each in a separate row
> of the same table. We do however accept that their is/may be a need for
> storing physical files greater than 2GB in size, thus Virtuoso Development
> agrees in principal that this limit should be increased, which shall be done
> sometime in the future.
> 
> 32Tera byte DB limit ...    Rdf_load    longwellHi
>>>> [Hugh] This refers to content not stored in Virtuoso SQL using its
>>>> virtualization features to access data from non-virtuoso sources. This also
>>>> covers procy server I from of we servers via redirects etc.
>>> 
>>> Ah, but this is specific for the non-VOS version, right?
>>> 
>>> [Hugh] This is possible with the VOS version also, it is only the virtual
>>> database feature of Virtuoso that is not available in open source form all
>>> other virtualization features are inlcuded.
> I'd be very interested in seeing some sample code using this.
> [Hugh] The Vizualization (hosting non-Virtuoso content) we refer to related to
> Virtuoso¹s .Net, Java, PHP, Python etc runtime hosting capabilities which are
> to be extended in the future and sources for those we have completed to date
> are part of the VOS archive.
> 
> Regards,
> Hugh
>>> 
>>>>> 1. I'm not entirely clear on whether virtuoso-t is a single-database or a
>>>>> multiple-database server. Can a single virtuoso-t host multiple databases?
>>>>> If not, does that mean each database would need their own connection
>>>>> ports? 
>>>> [Hugh] Multiple database instances can be start on the same machine using
>>>> the same virtuoso-t program with each instance being assigned a separate
>>>> server process.
>>> 
>>> Yes, by starting the same binary multiple times. But can a single running
>>> instance of virtuoso-t host multiple databases (like most DB products I'm
>>> familiar with), or does one instance service exactly one database?
>>> [Hugh] Within a Virtuoso Database instance (.db file) you can have multiple
>>> databases within, similarly to SQLServer.
> 
> I just had a look at the demo database, and it does look like you can host
> multiple databases (with multiple schemas inside those) in a single server
> instance. 
> 
> Emile
> 





Reply via email to