I worked with a large db (70GB) on a server that was cramped for space.
While I was trying to justify the purchase of SQL LiteSpeed to the
higher ups, the server was out of space every morning and occasionally
at other times. I had to be aggressive about shrinking the db and
keeping only a days worth of transaction and other logs... I didn't have
a choice but to shrink the db pretty often. Eventually I won the
LiteSpeed argument and the problem went away. So, Frank, if you don't
have enough file space for your db, shrink away. But use the arguments
against that as part of your justification for purchasing a product like
LiteSpeed. Good luck with your issue.

Carolyn J


-----Original Message-----
From: Anthon Mark J - DOA
[mailto:mssqldba-ezmlmshield-x5590896.[Email address protected]
Sent: Thursday, June 29, 2006 6:54 AM
To: LazyDBA Discussion
Subject: RE: Degrading database performance !!!!

Personally I'm not convinced of the degradation; it's pretty tough to
quantify. However, if you're concerned, do the shrink during a
maintenance window or after normal business hours.

-----Original Message-----
From: Frank Lau/IT
[mailto:mssqldba-ezmlmshield-x2988182.[Email address protected]
Sent: Wednesday, June 28, 2006 5:37 PM
To: LazyDBA Discussion
Subject: Degrading database performance !!!!


Hi,

Ok... Let's say to shrink it. However, most DBAs do not recommend
shrinking
the databases because the shrinking operation will degrade the
performance
of the databases.


How can I shrink the database without degrading the performance??


MS Sql Server LazyDBA home page