Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

insert statements and indexes  sql 2012

Posted on 2013-11-01
8
Medium Priority
?
335 Views
Last Modified: 2013-11-04
I have read that the execution of insert statements in sql slow down when a table has indexes.  Insert statements are regularly used with my rather large table.  Is there a way to index the table and at the same time optimize it so that the insert statements will execute faster?
0
Comment
Question by:al4629740
8 Comments
 
LVL 21

Expert Comment

by:oleggold
ID: 39618295
You could drop the index before insert and recreate after
0
 
LVL 21

Expert Comment

by:oleggold
ID: 39618296
if You use any graphic tool,such as quest toad for mssql free You can generate the table's ddl which will contain "create index" command and then  run it after Your insert is complete
0
 
LVL 21

Expert Comment

by:oleggold
ID: 39618298
i would though verify Your insert doesn't absolutely need any index by checking query execution plan
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 

Author Comment

by:al4629740
ID: 39618300
Drop and then recreate after each time?  This could happen a hundred times in a day?  Really?
0
 
LVL 21

Assisted Solution

by:oleggold
oleggold earned 500 total points
ID: 39618301
sometimes developers construct the dml/inserts based on the data already in the table which means they will run select using the indexes You may need ,after select is complete and insert command generated You can drop the indexes.
0
 
LVL 11

Assisted Solution

by:HuaMinChen
HuaMinChen earned 500 total points
ID: 39618317
You can create Indexed view on the same table to achieve better performance. Read
http://msdn.microsoft.com/en-us/library/ms191432.aspx
0
 
LVL 49

Assisted Solution

by:PortletPaul
PortletPaul earned 500 total points
ID: 39618473
>>Drop and then recreate after each time?
I don't believe that suggestion was made knowing it was needed hundreds of times a day (the assumption may have been you had a particularly large one-off set of inserts to perform for example). re-building the indexes multiple times a day would not be a good idea at all.

It is a trade-off between query speed and insert speed when you create indexes because for each index there are adjustments to the index for each insert.

HuaMinChen has pointed you to indexed views as an alternative strategy. Here you minimize the indexes on the table which is good for inserts, and you now have some indexes moved to the view of that table - however many/most of your queries would now need to use the view and not the table to take advantage of that approach. So there are "costs", or impacts, in all options.
0
 
LVL 70

Accepted Solution

by:
Scott Pletcher earned 500 total points
ID: 39621944
All non-clustered indexes are a trade-off.  Yes, they require maintaining during DELETEs, INSERTs and UPDATEs, and thus slow those statements down somewhat.  But, for indexes that are really needed, it's worth it, because of improved performance in queries.

Still, there are at least two big things you can do to help:
    1) remove underused or unused indexes.  You can use sys.dm_db_index_usage_stats to determine that, but be sure to wait long enough before removing indexes; for example, only one day or two may not be sufficient time for some indexes to determine whether they will be used or not.
    2) use filtered indexes whenever appropriate (filtered indexes are a great feature but are easy to forget/overlook).
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Windocks is an independent port of Docker's open source to Windows.   This article introduces the use of SQL Server in containers, with integrated support of SQL Server database cloning.
Microsoft Access has a limit of 255 columns in a single table; SQL Server allows tables with over 255 columns, but reading that data is not necessarily simple.  The final solution for this task involved creating a custom text parser and then reading…
Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties

782 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question