SQL report 'Disk Usage by Tables' Data and Indexes

In the SQL report 'Disk Usage by Tables', there are two columns, data and Indexes.
Does the number on Indexes column decrease after rebuilding index?

When I searched online about rebuilding index, for SQL 2008 standard, indexing is 'offline'. Does it mean that, if I want to schedule rebuilding index, I have to schedule to take database offline before indexing or will be done as a part of the maintenance plan for rebuilding index?

When I ran rebuilding index in the past, I didn't have to schedule to take offline the database, but applications can't access database. I wonder if it's just ok to schedule a maintenance plan without talking database offline first.

Also, when I test reorganizing index, to end users, it's the same effect, applications can't access database. But articles in internet say, reorganizing index is 'online' operation. I wonder what's the  difference to the view of end users if both operation makes database hung.
LVL 1
crcsupportAsked:
Who is Participating?
 
jogosConnect With a Mentor Commented:
A link to a solution that let you have more control on which indexes or fragmentation levels you want to target
http://ola.hallengren.com/
0
 
jogosConnect With a Mentor Commented:
The space used by an index will be better used, less fragmentation,  not necessary decrease.

If you use the online -option with your index rebuild the index maintenance has does not paralize your db, the process itself takes more time but your though
http://www.mssqltips.com/sqlservertip/2361/rebuilding-sql-server-indexes-using-the-online-option/
0
 
Scott PletcherConnect With a Mentor Senior DBACommented:
>> indexing is 'offline'.  Does it mean that, if I want to schedule rebuilding index, I have to schedule to take database offline before indexing or will be done as a part of the maintenance plan for rebuilding index? ... I didn't have to schedule to take offline the database, but applications can't access database. <<

Neither.  You don't have to take the database offline and the entire db is not inaccessible.

The index currently being rebuilt is unavailable; the table on which that index is built will also be unavailable for DELETE, INSERT and/or UPDATE, at least.


Maintenance plans are terrible inefficient and can cause more performance issues because they always rebuild every index, even in the index is not fragmented at all.  You should move to using a script that checks fragmentation levels and selectively rebuilds only the indexes that need it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.