network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 2 months |
| seen | May 2 at 21:24 | |
| stats | profile views | 2 |
|
Sep 14 |
awarded | Scholar |
|
Sep 14 |
accepted | Delete performance for LOB data in SQL Server |
|
Mar 7 |
revised |
Delete performance for LOB data in SQL Server Update with response from Paul Randal |
|
Mar 7 |
awarded | Supporter |
|
Mar 7 |
comment |
Delete performance for LOB data in SQL Server Thanks. That is exactly one of our options on the board. The table is a file system, and we are currently in the process of separating the binary data out to a completely separate database from the hierarchy meta. We could either do as you said and delete the hierarchy row, and have a GC process clean up orphaned LOB rows. Or have a delete timestamp with the data to accomplish the same goal. This is the route we may take if there is no satisfying answer to the problem. |
|
Mar 1 |
awarded | Student |
|
Mar 1 |
awarded | Editor |
|
Mar 1 |
revised |
Delete performance for LOB data in SQL Server added 966 characters in body |
|
Mar 1 |
asked | Delete performance for LOB data in SQL Server |
