Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sgondesi
Posting Yak Master
200 Posts |
 Posted - 2014-01-23 : 06:09:43
|
| Hello everyone..I read in one site that, an index rebuild requires space greater than or equal to the table on which it is defined and as a . Is that true?Already log grows when the index was first created right? Why does does it grows again when the index is rebuilt?-- Thanks and RegardsSrikar Reddy Gondesi,BTECH-IT 2013 Passed Out,Trainee for SQL Server Administration,Miracle Software systems, Inc. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-01-23 : 12:16:27
|
| Yes it's about 100% space of the index in the log file.It uses log space because it's a transaction. Anything that changes data/structure/etc requires log space. Log space is not the same thing as the data space. Log space is regarding transactions and recovery.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
 |
|
|
sgondesi
Posting Yak Master
200 Posts |
Posted - 2014-01-24 : 14:55:11
|
| Thank you for your valuable information madam.-- Thanks and RegardsSrikar Reddy Gondesi,BTECH-IT 2013 Passed Out,Trainee for SQL Server Administration,Miracle Software systems, Inc. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2014-01-25 : 15:18:53
|
| In case relevant: we run Log Backups every 2 minutes during index rebuild (normally ours are every 10 minutes) because Index Rebuild puts more strain on our Log files than any other activity in our databases. We also only rebuild indexes that are fragmented (rather than "Rebuild all indexes every time" <sigh!> |
|
|
|
|
|
|
Log space involved in Index Rebuilding