What is proper way of indexing on a table which contain large amount of data

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 - General » What is proper way of indexing on a table...

27 posts, Page 1 of 3

1 2 3 »»»

What is proper way of indexing on a table which contain large amount of data

Rate Topic

Display Mode

Topic Options

Author

Message

Anuj Rathi

Posted Tuesday, February 05, 2013 7:44 AM

SSC Journeyman

Group: General Forum Members
Last Login: Friday, March 22, 2013 3:01 AM
Points: 93, Visits: 163

Hi experts,
I have to optimize a database. I have almost done everything(modified stored procedures, implemented index also). But I am not satisfied & I am bit confused at this moment due to some sections.

There are few tables (contains millions of rows) which take part in public search. These tables also takes part in INSERT & UPDATE operations.

I have performed maximum possible normalization & cannot break my tables any more.
There is a main table & several related tables (so called child tables). Main table has 18 columns.
10 columns are numeric (int, bigint & numeric(18,2)), 4 columns are varchar (128), 2 columns are datetime and 2 columns are bit. Some columns are nullable also.

Search is based on different conditions & user can select one or more search conditions.
We are using dynamic query in our stored procedures. All columns can take part in "where" clause.
Now my questions are:

1. Should I create index on every columns? if yes, there will be 18 index (1 clustered & 17 non clustered). Is this correct approach?

2. Should I create covering index with all non clustered index or Is it sufficient to create covering index with only one non clustered index (on that column which always takes part in where clause).

Please suggest me proper approach.

Thanks in advance !

Post #1415845

Grant Fritchey

Posted Tuesday, February 05, 2013 8:45 AM

SSChampion

Group: General Forum Members
Last Login: Yesterday @ 3:40 PM
Points: 13,380, Visits: 25,164

This is a gigantic topic.

I'm not going to be able to give you specific guidance based on a generic problem as you've outlined. Sorry.

It sounds like you're creating a "report on anything" page and you're finding, as everyone does, that it's very hard to optimize those. The fact is, in most cases, there are patterns to what the users are going to access. Seldom is it true that they will search on anything. Generally there are related columns that will always be used for specific types of searches. You need to identify these patterns, then index accordingly.

Putting a single index on each column is an extremely poor choice. It is likely that the majority of those indexes will never be used by any search criteria. You will still have to maintain them through all inserts, updates & deletes, adding significantly to your overhead.

Dynamic t-sql is the way to go with this type of query. Just make sure you're using sp_executesql and parameters and not merely building a sql string and executing it. The first method ensures at least some plan reuse. The second ensures none.

Other than that, I'd say recognize the access patterns and then build indexes to support them. In most circumstances, compound keys and included columns work much better than single column indexes, but it really, really depends on exactly what the T-SQL code looks like.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software

Post #1415904

GilaMonster

Posted Tuesday, February 05, 2013 8:53 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 12:38 AM
Points: 37,725, Visits: 29,981

Grant Fritchey (2/5/2013)

Other than that, I'd say recognize the access patterns and then build indexes to support them. In most circumstances, compound keys and included columns work much better than single column indexes, but it really, really depends on exactly what the T-SQL code looks like.

This.

You analyse common patterns and index to support those.

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1415915

Anuj Rathi

Posted Tuesday, February 05, 2013 9:12 AM

SSC Journeyman

Group: General Forum Members
Last Login: Friday, March 22, 2013 3:01 AM
Points: 93, Visits: 163

Hi Gail, Fritchey,

Thanks for your reply.

Fritchey, thank you very much. I have found my first approach which I have to do.
We are not using sp_executesql. So, this is my step. I am going to change the process. Now, I am afraid because developers have created all SPs using sql string. We haven't used parameters.

"Other than that, I'd say recognize the access patterns and then build indexes to support them. In most circumstances, compound keys and included columns work much better than single column indexes, but it really, really depends on exactly what the T-SQL code looks like."

can you please let me know how can I do this approach?

Post #1415931

Grant Fritchey

Posted Tuesday, February 05, 2013 9:25 AM

SSChampion

Group: General Forum Members
Last Login: Yesterday @ 3:40 PM
Points: 13,380, Visits: 25,164

You've got two options there. Well, actually, you have to do both. First, talk to the business people to understand what they're actually going to do, not what they're asking for. Second, capture the queries as they come in and match that with what you know about the structure and their access methods. But the main thing is talking to the business to understand what they're doing.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software

Post #1415944

GilaMonster

Posted Tuesday, February 05, 2013 9:29 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 12:38 AM
Points: 37,725, Visits: 29,981

http://sqlinthewild.co.za/index.php/2011/11/11/sql-university-advanced-indexing-indexing-strategies/

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1415948

Anuj Rathi

Posted Tuesday, February 05, 2013 9:37 AM

SSC Journeyman

Group: General Forum Members
Last Login: Friday, March 22, 2013 3:01 AM
Points: 93, Visits: 163

Hi Fritchey,

We have made the SQL like this,

IF @inbCityID IS NOT NULL AND @inbCityID > 0
BEGIN
SET @SqlCondition = @SqlCondition + ' AND vaa.CityID = ' + CONVERT(VARCHAR(50), @inbCityID);
END

(this is only a block of code)
& Finally we use below code:
EXECUTE SP_EXECUTESQL @FinalSql;

Should I change above structure to parametrized structure & then I should pass the parameters to SP_EXECUTESQL.

Post #1415954

GilaMonster

Posted Tuesday, February 05, 2013 9:38 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 12:38 AM
Points: 37,725, Visits: 29,981

Yes, absolutely yes.

As you have it, it's a security risk (SQL injection) and subject to poor plan caching and reuse.

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1415955

Anuj Rathi

Posted Tuesday, February 05, 2013 9:40 AM

SSC Journeyman

Group: General Forum Members
Last Login: Friday, March 22, 2013 3:01 AM
Points: 93, Visits: 163

Gail, thanks for the link,

Post #1415956

Anuj Rathi

Posted Tuesday, February 05, 2013 10:44 AM

SSC Journeyman

Group: General Forum Members
Last Login: Friday, March 22, 2013 3:01 AM
Points: 93, Visits: 163

Hi Gail,
I have changed my one stored procedure. As you have the code block which I posted. Now that block will look like this:
IF @inbCityID IS NOT NULL AND @inbCityID > 0
BEGIN
SET @SqlCondition = @SqlCondition + N' AND vaa.CityID = @inbCityID';
END

I have just one question. When I will call the sp_executesql & will pass the parameters, Can I pass all parameters (approx 14) regardless of query.
Means in above code block, if @inbCityID is 0 then above condition will not be included in our final sql string. Can I pass my all parameters (including @inbCityID) because we don't know that this condition will become true or false.

I have checked by executing the procedure (& passed all parameters) where only one condition was true, SP is running without any error.

I have just asked because of any performance consideration. Is there any performance impact if I pass more parameters. I have included all parameters in params definition. I googled but didn't find any answer, that's why I am asking.

Post #1415997

« Prev Topic | Next Topic »

27 posts, Page 1 of 3

1 2 3 »»»

Permissions