By the way, I have tried to compress the big db file using gzip, and I can
get over 1:4 compression ratio, so I think there is still a lot of room in
the db file that are not very important.
Is there a function in virtuoso that can be post-loading optimization to
reduce the db file size, which may
I have used this:
SELECT COUNT(*) FROM SYS_PROCEDURES WHERE P_NAME = :name
> Le 2015-04-11 à 08:45, Gang Fu a écrit :
>
> Hi,
>
> I want to ask how can we check the existence of a stored procedure before we
> drop it?
> We need to drop the stored procedure before we create it, otherwise, ther
Thank you very much, Morty! You are right, 'split' plus 'cat' is a better
option, since the server can start immediately with the rebuild db file.
Is there a way to test whether a stored procedure exists? I have another
ticket about this question, but I have not gotten any reply yet there :)
On W
Hi,
I just want to ping this question, in case it was missed
Best,
Gang
On Sat, Apr 11, 2015 at 8:45 AM, Gang Fu wrote:
> Hi,
>
> I want to ask how can we check the existence of a stored procedure before
> we drop it?
> We need to drop the stored procedure before we create it, otherwise, t
Thank you very much, Hugh! You are right, we are going to update the large
data set on weekly basis, and the updates are on the scale of a couple of
millions, or less than that. The bulk loader with delete option sounds good
for me, but only the nquad files are allowed. Our input files are in ttl,
