There are two kind of storage in database. Row Store and Column Store. Row store does exactly as the name suggests – stores rows of data on a page – and column store stores all the data in a column on the same page. These columns are much easier to search – instead of a query searching all the data in an entire row whether the data is relevant or not, column store queries need only to search much lesser number of the columns. This means major increases in search speed and hard drive use. Additionally, the column store indexes are heavily compressed, which translates to even greater memory and faster searches. I am sure this looks very exciting and it does not mean that you convert every single index from row store to columnstore index. One has to understand the proper places where to use row store or column store indexes. Let us understand in this article what is the difference in Columnstore type of index.
SQLAuthority News – Tomorrow Online Session – Ancient Trade of Performance Tuning – Index, Beyond Index and No Index
Today in few hours I am going to present on my very favorite subject of performance tuning. You can read more about this sessions over here. This presentation is based on the famous book ‘The Art of War’ written in sixth century BC by Sun Tzu. Index is usually a…
Read MoreSQLAuthority News – Online Session – Ancient Trade of Performance Tuning – Index, Beyond Index and No Index
Performance Tuning has been my favorite subject always. I love this subject the most. I personally have enjoyed every aspect of performance tuning. Quite often I have seen that when it is about performance, people end up talking about Indexes. Index for sure can help performance, but it is like…
Read MorePuzzle – Usage of New Index Hints – ForceSeek and ForceScan
Tomorrow is the weekend. I just thought, let us explore something new but a quick puzzle to explore about index hints.
SQL Server Denali has new Query Hint – FORCESCAN. In earlier version of SQL Server we already have Query Hint FORCESEEK but now the counter part also exists. The quick understanding is there will be cases when FORCESEEK or FORCESCAN will be helpful and improve the performance of the query.
SQL SERVER – Query to Find Duplicate Indexes – Script to Find Redundant Indexes
I was recently delivering session on Performance Tuning subject. I was asking if there is any harm having duplicate indexes. Of course, duplicate indexes are nothing but overhead on the database system. Database system has to maintain two sets of indexes when it has to do update, delete, insert on…
Read MoreInterview Questions and Answers – Frequently Asked Questions – Day 6 of 31
Please read the Introductory Post before continuing reading interview questions and answers. Some more questions are included in the blog.
SQL SERVER – Solution – Puzzle – Statistics are not Updated but are Created Once
Earlier I asked puzzle why statistics are not updated. Read the complete details over here: Statistics are not Updated but are Created Once In the question I have demonstrated even though statistics should have been updated after lots of insert in the table are not updated.(Read the details SQL SERVER –…
Read More