I find shrinking the files individually is a much more reliable way to do
so. Also backup the log file with the truncate option to free up any info
there then do the shrink.


Ryan


|---------+-------------------------------------------------------->
| | "Juan Vera " |
| | <mssqldba-ezmlmshield-x65876943.[Email Address Removed] | azyDBA.com> |
| | |
| | |
| | |
| | 29/06/2005 09:39 AM |
| | |
|---------+-------------------------------------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
| |
| To: "LazyDBA Discussion" <[Email address protected] |
| cc: |
| Subject: Shrinking a Database |
>-------------------------------------------------------------------------------------------------------------------------------|




Hi, All

I'm having a problem shrinking a database - running:
dbcc shrinkdatabase(dbName, 10)
I get a 170GB database not shrunk at all, while reporting 90GB of free
space left at the end.

Is there something I'm missing in how to run the command, or another
explicit way of deallocating space from the database to reduce the size fo
the device?

TIA

Juan Cristián




---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html








_______________________________________________________________________________
Unencrypted electronic mail is not secure and may not be authentic.
If you have any doubts as to the contents please telephone to confirm.

This electronic transmission including any attachments is intended only
for those to whom it is addressed. It may contain copyright material or
information that is confidential, privileged or exempt from disclosure by law.
Any claim to privilege is not waived or lost by reason of mistaken transmission
of this information. If you are not the intended recipient you must not
distribute or copy this transmission and should please notify the sender.
Your costs for doing this will be reimbursed by the sender.

We do not accept liability in connection with computer virus, data corruption,
delay, interruption, unauthorised access or unauthorised amendment.
_______________________________________________________________________________


MS Sql Server LazyDBA home page