On 13/01/2016, at 3:30 PM, Saulo Merlo wrote:
So.. I have a Query that is taking too long to complete.
OLD QUERY:
SELECT file.inode_idAS file_id, file.parent_inode_id AS file_group,
file.relative_path AS file_type, file.file_data AS file_binary,
file.node_full_path AS
Anyone who can help with this please?
Thanks
Sent from my phone
> On 13/01/2016, at 3:30 PM, Saulo Merlo wrote:
>
> So.. I have a Query that is taking too long to complete.
>
> OLD QUERY:
>
>> SELECT
>
>> file.inode_idAS file_id,
>
>> file.parent_inode_id AS file_group,
>
>>
So.. I have a Query that is taking too long to complete.
OLD QUERY:
SELECT file.inode_idAS file_id, file.parent_inode_id AS file_group,
file.relative_path AS file_type, file.file_data AS file_binary,
file.node_full_path AS file_name, file.last_modified AS date_createdFR
A. Kretschmer wrote:
am 31.07.2006, um 15:55:39 +0100 mailte Richard Huxton folgendes:
Christian Rengstl wrote:
My version is 8.1.4. Here is the plan for the query, it's performed on a
Total runtime: 1903.894 ms
And yes i have indexes on both pid (varchar(15)
I meant that i have an index on pid and one on crit.
>>> "A. Kretschmer" <[EMAIL PROTECTED]> 31.07.06 17.16
Uhr >>>
am 31.07.2006, um 15:55:39 +0100 mailte Richard Huxton folgendes:
> Christian Rengstl wrote:
> >My version is 8.1.4. Here is the plan for the query, it's performed
on a
> >
am 31.07.2006, um 15:55:39 +0100 mailte Richard Huxton folgendes:
> Christian Rengstl wrote:
> >My version is 8.1.4. Here is the plan for the query, it's performed on a
> >Total runtime: 1903.894 ms
> >And yes i have indexes on both pid (varchar(15)) and crit(va
Christian Rengstl wrote:
My version is 8.1.4. Here is the plan for the query, it's performed on a
smaller table, though because i can't access the biggest table at the
moment:
QUERY PLAN
My version is 8.1.4. Here is the plan for the query, it's performed on a
smaller table, though because i can't access the biggest table at the
moment:
QUERY PLAN
-
am 31.07.2006, um 15:32:19 +0200 mailte Christian Rengstl folgendes:
> Hi list,
>
> i have a problem with creating a query and i hope somebody can give me
> some hints. I have the following table
> pid(varchar), crit(varchar), val1(varchar), val2(varchar),
> iDate(timestamp)
> where there are up
Hi list,
i have a problem with creating a query and i hope somebody can give me
some hints. I have the following table
pid(varchar), crit(varchar), val1(varchar), val2(varchar),
iDate(timestamp)
where there are up to 63 million lines with 1500 distinct pids and
around 42000 distinct crits:
pid c
Look into inheritance. It makes this easier. However, I don't care
which RDBMS you use, management of 1000 identical tables is going to
be a real pain and I think that everyone here will probably suggest
that it is not exactly a sane thing to do.
Thank you, Chris. I have omitted two import
Poul Jensen wrote:
you want to create 1 million tables, all with one of
2 schemas?
I started out with a schema for each file, thinking I could utilize
the schema
structure in queries, but I don't see how. Schemas are useful for
grouping
tables according to users/owners. Other than t
you want to create 1 million tables, all with one of
2 schemas?
I started out with a schema for each file, thinking I could utilize
the schema
structure in queries, but I don't see how. Schemas are useful for grouping
tables according to users/owners. Other than that, do they add anyth
Poul Jensen <[EMAIL PROTECTED]> writes:
>>you want to create 1 million tables, all with one of
>>2 schemas?
>>
>>
>
> I started out with a schema for each file, thinking I could utilize
> the schema
> structure in queries, but I don't see how. Schemas are useful for grouping
> tables according t
Thank you very much for your response! It leads to another couple of
questions:
I'm building a database containing key parameters for ~500,000 data
files. The design I found logical is
Two tables for each file:
1) Larger table with detailed key parameters
(10-15 columns, ~1000 rows), call i
On Sat, 2005-09-03 at 00:59 -0800, Poul Jensen wrote:
> I'm building a database containing key parameters for ~500,000 data
> files. The design I found logical is
>
> Two tables for each file:
> 1) Larger table with detailed key parameters
> (10-15 columns, ~1000 rows), call it large_table
> 2
I'm building a database containing key parameters for ~500,000 data
files. The design I found logical is
Two tables for each file:
1) Larger table with detailed key parameters
(10-15 columns, ~1000 rows), call it large_table
2) Small table with file summary
(~30 columns, 1 row), call it sma
17 matches
Mail list logo
