![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We are running SQL Server 2000 SP4. One of the db instances has grown pretty rapidly and we're using the front-end application to remove unnecessary data, but the actual .mdf file doesn't change. And that's after a shrink database operation. I've verified that the app is actually removing unneeded records buy using their reporting tool. Anyone have any thoughts on this? |
#3
| |||
| |||
|
|
PaddleHard (ipaddle4... (AT) gmail (DOT) com) writes: We are running SQL Server 2000 SP4. One of the db instances has grown pretty rapidly and we're using the front-end application to remove unnecessary data, but the actual .mdf file doesn't change. And that's after a shrink database operation. I've verified that the app is actually removing unneeded records buy using their reporting tool. Anyone have any thoughts on this? There is always reason to be very careful with shrinking databases. Particularly, if the database will grow again it is a meaningless - and harmful - operation. It may be that the space in the database in the database is taken up by other tables than what the fronr-end is deleting from. This query: * *SELECT object_name(id), * * *FROM * sysindexes * *WHERE *index_id IN (0, 1, 255) * *ORDER BY reserved DESC lists the tables in desceding order with regards to size. Reserved is the size in as counted in 8K pages. -- Erland Sommarskog, SQL Server MVP, esq... (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008:http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005:http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000:http://www.microsoft.com/sql/prodinf...ons/books.mspx |
![]() |
| Thread Tools | |
| Display Modes | |
| |