meta user
network profile
| bio | website | |
|---|---|---|
| location | Nashville, TN | |
| age | 26 | |
| visits | member for | 1 year, 6 months |
| seen | Nov 14 '12 at 19:09 | |
| stats | profile views | 3 |
|
Sep 17 |
awarded | Popular Question |
|
Nov 17 |
answered | Database-backed website configuration |
|
Nov 14 |
awarded | Scholar |
|
Nov 14 |
comment |
SQL Rebuild Index, Recovery Model, and db log filesize? I'm marking this as the answer, because I believe we're going to look at custom scripting to do the index rebuild, based on the current fragmentation percentage of each index. And we'll also implement a transaction log dump in the script to clear up space. |
|
Nov 14 |
accepted | SQL Rebuild Index, Recovery Model, and db log filesize? |
|
Nov 14 |
comment |
Meaning of SSMS database icon preceded by scroll with red x Yep, what Martin said. Check any policies you may have setup. |
|
Nov 14 |
comment |
MySQL - How do you enter a record with only whitespace “ ”? VARCHAR should keep your whitespaces. Just confirmed on MySQL version 5.1.56. |
|
Nov 14 |
awarded | Supporter |
|
Nov 12 |
awarded | Teacher |
|
Nov 12 |
answered | Personal Instance on Personal Computer |
|
Nov 12 |
comment |
SQL Rebuild Index, Recovery Model, and db log filesize? If we ran a full backup prior to the rebuild job, then switched to simple mode for the rebuild. Once the rebuild job finishes if I switch back to simple and run another full backup I should be covered, correct? Aside from the 15 minutes or so that the rebuild task is running? I'm likely going to go with the route of building a script to do the index rebuild, and incorporate log backups throughout the script. However, I think in the long run, that will still require just as much additional HDD space. But I think that will still be more beneficial than having a 25gb log file to truncate. |
|
Nov 12 |
awarded | Student |
|
Nov 11 |
asked | SQL Rebuild Index, Recovery Model, and db log filesize? |
