Database Space Available Is Zero Even AFter Running Backup Log With No Truncate

I refreshed the SQL server name after rnning a backup log with no
truncate ....and still found out that space available size is still 0!
I also shrunk the Trans Log and still the same rusults.
Would very much appreciate your help
Thank you
*** Sent via Developersdex http://www.codecomments.com ***Hi,
What is the Recovery model of your database?
If it is FULL OR BULK_LOGGED then
If you need the transaction log backup execute below to clear the
Transaction log:-
backup log <dbname> to disk='d:\backup\dbname.trn
Incase if you do not require the transaction log backup go for;
backup log <dbname> with truncate_only
The above commands will clear the log , bit to reduce the physical LDF file
size you will have to execute the below command:-
DBCC SHRINKFILE (db1_log1_logical_name,truncat_eonly)
After doing these execute the below command to get the log size
dbcc sqlperf(logspace)
Thanks
Hari
SQL Server MVP
"mike" <-nospam@.yahoo.com> wrote in message
news:%23F7ieaVkFHA.2852@.TK2MSFTNGP14.phx.gbl...
> I refreshed the SQL server name after rnning a backup log with no
> truncate ....and still found out that space available size is still 0!
> I also shrunk the Trans Log and still the same rusults.
> Would very much appreciate your help
> Thank you
>
>
> *** Sent via Developersdex http://www.codecomments.com ***|||did you hear mike <-nospam@.yahoo.com> say in news:#F7ieaVkFHA.2852
@.TK2MSFTNGP14.phx.gbl:

> AFter Running Backup Log With No Truncate
sorry, but wouldn't this be the problem? if you wish to remove the
committed transactions from the log you should remove the no_truncate
option.
http://msdn.microsoft.com/library/d...rl=/library/en-
us/tsqlref/ts_ba-bz_35ww.asp
Neil MacMurchy
http://spaces.msn.com/members/neilmacmurchy
http://spaces.msn.com/members/mctblogs|||thank you. It worked, perfectly-
Mike
*** Sent via Developersdex http://www.codecomments.com ***

Database Space Available Is Zero Even AFter Running Backup Log With No Truncate

I refreshed the SQL server name after rnning a backup log with no
truncate ....and still found out that space available size is still 0!
I also shrunk the Trans Log and still the same rusults.
Would very much appreciate your help
Thank you
*** Sent via Developersdex http://www.codecomments.com ***
Hi,
What is the Recovery model of your database?
If it is FULL OR BULK_LOGGED then
If you need the transaction log backup execute below to clear the
Transaction log:-
backup log <dbname> to disk='d:\backup\dbname.trn
Incase if you do not require the transaction log backup go for;
backup log <dbname> with truncate_only
The above commands will clear the log , bit to reduce the physical LDF file
size you will have to execute the below command:-
DBCC SHRINKFILE (db1_log1_logical_name,truncatXeonly)
After doing these execute the below command to get the log size
dbcc sqlperf(logspace)
Thanks
Hari
SQL Server MVP
"mike" <-nospam@.yahoo.com> wrote in message
news:%23F7ieaVkFHA.2852@.TK2MSFTNGP14.phx.gbl...
> I refreshed the SQL server name after rnning a backup log with no
> truncate ....and still found out that space available size is still 0!
> I also shrunk the Trans Log and still the same rusults.
> Would very much appreciate your help
> Thank you
>
>
> *** Sent via Developersdex http://www.codecomments.com ***
|||did you hear mike <-nospam@.yahoo.com> say in news:#F7ieaVkFHA.2852
@.TK2MSFTNGP14.phx.gbl:

> AFter Running Backup Log With No Truncate
sorry, but wouldn't this be the problem? if you wish to remove the
committed transactions from the log you should remove the no_truncate
option.
http://msdn.microsoft.com/library/de...l=/library/en-
us/tsqlref/ts_ba-bz_35ww.asp
Neil MacMurchy
http://spaces.msn.com/members/neilmacmurchy
http://spaces.msn.com/members/mctblogs
|||thank you. It worked, perfectly-
Mike
*** Sent via Developersdex http://www.codecomments.com ***

Database size shrunk

I will like to request for understanding with regards to SQL data size.

On Friday, 21 March, I checked from the SQL Server Enterpise Manager that my Data Size was 30 MB.

I then had my database quota size increased.

However, on Monday 24 March, I noted that the data size has shrunk to 24 MB even though my client has added about 7k+ of records to the database since.

Today on 25 March, the database showed 15 MB instead. I checked my records and there was nothing lost in them. The number remains the same or slightly higher. This is because they have almost completed the porting of the data.

I am confused as to the difference in the display of Data Size. It has lead me to a wrong decision earlier to upgrade to 45 MB when in actual fact, the data doesnt even take more than 16 MB.

I have during the time truncated the transaction logs. Could this be the cause of the database size to shrink?Check whether AUTO_SHRINK option is used.|||Originally posted by Satya
Check whether AUTO_SHRINK option is used.

Thanks for replying

I just checked and AUTO_shrink is off

Would there be anything else that could cause it to shrink?sql

Database Size

I have a database that I have backed-up and shrunk to try
and get it as small as possible. I was expecting to get
the size down under 10M. I have deleted most of the data
in the tables and as small as it will get is 38M. I
repeated the back-up and shrinking multiple times. Any
suggestions would be greatly appreciated.
Thanks,
Bill
Backups will not shrink your database. What other methods are you trying to
shrink the database? Norrmally you would use DBCC SHRINKFILE. Depending on
how your tables are architechted, 38 MB may be as small as it will go.
Jim
"bill" <anonymous@.discussions.microsoft.com> wrote in message
news:2dac01c4287f$b34dbb30$a001280a@.phx.gbl...
> I have a database that I have backed-up and shrunk to try
> and get it as small as possible. I was expecting to get
> the size down under 10M. I have deleted most of the data
> in the tables and as small as it will get is 38M. I
> repeated the back-up and shrinking multiple times. Any
> suggestions would be greatly appreciated.
> Thanks,
> Bill