network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 6 months |
| seen | Nov 19 '12 at 9:44 | |
| stats | profile views | 3 |
|
Mar 27 |
awarded | Popular Question |
|
Nov 16 |
comment |
SQL Server database size didn't decrease after deleting large number of rows. 3. Repeat until there's just enough space to forget about this problem for a couple of years. Thanks guys, you've become real help to me. |
|
Nov 16 |
comment |
SQL Server database size didn't decrease after deleting large number of rows. What i have looks like this: Almost full partition, no place to write new logs, and lot's of old unneeded info (from 2008, for ex). Here's how my algorythm looked like after reading all your useful advices (from which I took only "shrink the base" part, sorry, that's the cost of war): 1. Delete a part of info, just as much as left free space let's us. Query i used: delete from dbNameHere where logTime >= 'some_date' and logTime <= 'some_date' 2. Shrink the database to release unused space from db itself and clear transaction log (no command lines, used MS SQL 2005 interface) |
|
Nov 16 |
awarded | Student |
|
Nov 8 |
asked | SQL Server database size didn't decrease after deleting large number of rows. |
