You've already had some good advice, but there's something much more simpler
that will also give you a significant boost: a covering index.
Simply put, the engine is smart enough to not bother with row lookups if
everything you asked for is already in the index it was using. You'll need to
Hi,
I have in my server database some tables that are too much big and produce
some slow query, even with correct indexes created.
For my application, it's necessary to have all the data because we make an
authentication process with RADIUS users (AAA protocol) to determine if one
user can
Am 15.05.2014 14:26, schrieb Antonio Fernández Pérez:
I have in my server database some tables that are too much big and produce
some slow query, even with correct indexes created.
For my application, it's necessary to have all the data because we make an
authentication process with RADIUS
On Thu, May 15, 2014 at 4:14 AM, Johan De Meersman vegiv...@tuxera.be wrote:
You've already had some good advice, but there's something much more simpler
that will also give you a significant boost: a covering index.
Simply put, the engine is smart enough to not bother with row lookups if
- Original Message -
From: Larry Martell larry.mart...@gmail.com
Subject: Re: Performance boost by splitting up large table?
This table is queried based on requests from the users. There are 10
different lookup columns they can specify, and they can provide any or
That makes it
On Thu, May 15, 2014 at 11:01 AM, Johan De Meersman vegiv...@tuxera.be wrote:
- Original Message -
From: Larry Martell larry.mart...@gmail.com
Subject: Re: Performance boost by splitting up large table?
This table is queried based on requests from the users. There are 10
different
