Citando James Harper :
> Does MySQL have a 'profiler' tool like MSSQL does? I spend most of my
> time in MSSQL and if some operation is running slow I just attach the
> profiler to it and capture the queries and focus on the ones that are
> taking most of the time.
>
> James
What is the impact
On Saturday 20 June 2009 08:51:53 Tom Sommer wrote:
> Tom Sommer wrote:
> > Mike Holden wrote:
> >> Jari Fredriksson wrote:
> INSERT INTO Filename( Name )
> SELECT a.Name
> FROM (
>
> SELECT DISTINCT Name
> FROM batch
> ) AS a
> WHERE NOT
> EXISTS (
> >>
Tom Sommer wrote:
> Mike Holden wrote:
>
>> Jari Fredriksson wrote:
>>
>>
INSERT INTO Filename( Name )
SELECT a.Name
FROM (
SELECT DISTINCT Name
FROM batch
) AS a
WHERE NOT
EXISTS (
SELECT Name
FROM Filename AS f
WHERE f.Na
Jari Fredriksson wrote:
>> James Harper wrote:
>>> The subquery returns a very small result set (0 or 1,
>>> assuming you use DISTINCT) and so isn't too inefficient.
>>> It's when you say 'WHERE NOT EXISTS (SOME QUERY WITH
>>> LOTS OF RESULTS)' that you start to really bog down
>> True, but if the
Jari Fredriksson wrote:
>> James Harper wrote:
>>> The subquery returns a very small result set (0 or 1,
>>> assuming you use DISTINCT) and so isn't too inefficient.
>>> It's when you say 'WHERE NOT EXISTS (SOME QUERY WITH
>>> LOTS OF RESULTS)' that you start to really bog down
>> True, but if the
> James Harper wrote:
>> The subquery returns a very small result set (0 or 1,
>> assuming you use DISTINCT) and so isn't too inefficient.
>> It's when you say 'WHERE NOT EXISTS (SOME QUERY WITH
>> LOTS OF RESULTS)' that you start to really bog down
>
> True, but if the outer query contains a very
>
> James Harper wrote:
> > The subquery returns a very small result set (0 or 1, assuming you
use
> > DISTINCT) and so isn't too inefficient. It's when you say 'WHERE NOT
> > EXISTS (SOME QUERY WITH LOTS OF RESULTS)' that you start to really
bog
> > down
>
> True, but if the outer query contains
James Harper wrote:
> The subquery returns a very small result set (0 or 1, assuming you use
> DISTINCT) and so isn't too inefficient. It's when you say 'WHERE NOT
> EXISTS (SOME QUERY WITH LOTS OF RESULTS)' that you start to really bog
> down
True, but if the outer query contains a very large num
> > INSERT INTO Filename(Name)
> > SELECT DISTINCT Name
> > FROM batch AS a
> > WHERE NOT EXISTS
> > (
> > SELECT Name
> > FROM Filename AS f
> > WHERE f.Name = a.Name
> > )
>
> You may also want to consider using a JOIN rather than a subquery with
a
> NOT EXISTS, something like (untes
Mike Holden wrote:
> Jari Fredriksson wrote:
>
>>> INSERT INTO Filename( Name )
>>> SELECT a.Name
>>> FROM (
>>>
>>> SELECT DISTINCT Name
>>> FROM batch
>>> ) AS a
>>> WHERE NOT
>>> EXISTS (
>>>
>>> SELECT Name
>>> FROM Filename AS f
>>> WHERE f.Name = a.Name
>>> )
>>>
>>>
>> That looks s
Jari Fredriksson wrote:
>>
>> INSERT INTO Filename( Name )
>> SELECT a.Name
>> FROM (
>>
>> SELECT DISTINCT Name
>> FROM batch
>> ) AS a
>> WHERE NOT
>> EXISTS (
>>
>> SELECT Name
>> FROM Filename AS f
>> WHERE f.Name = a.Name
>> )
>>
>
> That looks silly.
>
> I would write it shorter as
>
> INSERT
> On Fri, 19 Jun 2009 09:51:20 +0200, Tom Sommer said:
>
> Martin Simmons wrote:
> >> On Thu, 18 Jun 2009 17:11:04 +0200, Michel Meyers said:
> >>
> >> Martin Simmons wrote:
> >>
> On Wed, 17 Jun 2009 13:48:58 +0200, Tom Sommer said:
>
> On Fri, 19 Jun 2009 03:00:54 +0300, Jari Fredriksson said:
>
> >
> > INSERT INTO Filename( Name )
> > SELECT a.Name
> > FROM (
> >
> > SELECT DISTINCT Name
> > FROM batch
> > ) AS a
> > WHERE NOT
> > EXISTS (
> >
> > SELECT Name
> > FROM Filename AS f
> > WHERE f.Name = a.Name
> > )
> >
Martin Simmons wrote:
>> On Thu, 18 Jun 2009 17:11:04 +0200, Michel Meyers said:
>>
>> Martin Simmons wrote:
>>
On Wed, 17 Jun 2009 13:48:58 +0200, Tom Sommer said:
Martin Simmons wrote:
>> On Tue, 16 Jun 2009 1
Jari Fredriksson wrote:
>> INSERT INTO Filename( Name )
>> SELECT a.Name
>> FROM (
>>
>> SELECT DISTINCT Name
>> FROM batch
>> ) AS a
>> WHERE NOT
>> EXISTS (
>>
>> SELECT Name
>> FROM Filename AS f
>> WHERE f.Name = a.Name
>> )
>>
>>
>
> That looks silly.
>
> I would write it shorter as
>
> I
>
> INSERT INTO Filename( Name )
> SELECT a.Name
> FROM (
>
> SELECT DISTINCT Name
> FROM batch
> ) AS a
> WHERE NOT
> EXISTS (
>
> SELECT Name
> FROM Filename AS f
> WHERE f.Name = a.Name
> )
>
That looks silly.
I would write it shorter as
INSERT INTO Filename(Name)
SELECT DISTINCT Name
FRO
> On Thu, 18 Jun 2009 17:11:04 +0200, Michel Meyers said:
>
> Martin Simmons wrote:
> >> On Wed, 17 Jun 2009 13:48:58 +0200, Tom Sommer said:
> >> Martin Simmons wrote:
> On Tue, 16 Jun 2009 15:05:18 +0200, Tom Sommer said:
>
> Hi,
>
> I have a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Simmons wrote:
>> On Wed, 17 Jun 2009 13:48:58 +0200, Tom Sommer said:
>> Martin Simmons wrote:
On Tue, 16 Jun 2009 15:05:18 +0200, Tom Sommer said:
Hi,
I have a somewhat pressing problem with th
> On Wed, 17 Jun 2009 13:48:58 +0200, Tom Sommer said:
>
> Martin Simmons wrote:
> >> On Tue, 16 Jun 2009 15:05:18 +0200, Tom Sommer said:
> >>
> >> Hi,
> >>
> >> I have a somewhat pressing problem with the performance of my Bacula
> >> installation.
> >>
> >> My MySQL dat
Martin Simmons wrote:
>> On Tue, 16 Jun 2009 15:05:18 +0200, Tom Sommer said:
>>
>> Hi,
>>
>> I have a somewhat pressing problem with the performance of my Bacula
>> installation.
>>
>> My MySQL database currently holds 247,342,127 (36GB) records in the File
>> table, and 78,57
> On Tue, 16 Jun 2009 15:05:18 +0200, Tom Sommer said:
>
> Hi,
>
> I have a somewhat pressing problem with the performance of my Bacula
> installation.
>
> My MySQL database currently holds 247,342,127 (36GB) records in the File
> table, and 78,576,199 (10GB) records in the Filename table.
>
Hi,
I have a somewhat pressing problem with the performance of my Bacula
installation.
My MySQL database currently holds 247,342,127 (36GB) records in the File
table, and 78,576,199 (10GB) records in the Filename table.
Since 3.0.0, but even more since 3.0.1, I have a problem with queries
being
22 matches
Mail list logo