Shrink Log file for all Databases

Question

Shrink Log file for all Databases

David Bird

SSCarpal Tunnel

Points: 4669
More actions
September 24, 2007 at 2:08 pm

#175142

Comments posted to this topic are about the item Shrink Log file for all Databases
David Bird

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

F. van 't Hoff Valued Member Points: 59 More actions · Answer 1

I've tried this script, but it will only work if there are no spaces in the db_name. We have a database named Mediabin Repository and when I run this script, I'll get the following error:

"Msg 911, Level 16, State 1, Line 1"

"Could not locate entry in sysdatabases for database 'MediaBin'. No entry found with that name. Make sure that the name is entered correctly."

What is the correct way to run this script when there are spaces in the database name?

reddi_arjun Say Hey Kid Points: 669 More actions · Answer 2

reddi_arjun

Say Hey Kid

Points: 669

March 18, 2013 at 7:29 am

#1598047

Thanks a lot.

The script was very helpful.

TheSQLGuru SSC Guru Points: 134017 More actions · Answer 3

reddi_arjun (3/18/2013)
Thanks a lot.
The script was very helpful.

PLEASE DO NOT DO THIS!!! IT IS A HORRIBLE, HORRIBLE THING TO DO ON YOUR SQL SERVER!!!

Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 4

F. van 't Hoff (11/29/2011)
I've tried this script, but it will only work if there are no spaces in the db_name. We have a database named Mediabin Repository and when I run this script, I'll get the following error:
"Msg 911, Level 16, State 1, Line 1"
"Could not locate entry in sysdatabases for database 'MediaBin'. No entry found with that name. Make sure that the name is entered correctly."
What is the correct way to run this script when there are spaces in the database name?

Because your database name has a space in it, you would need to put it in brackets, [Mediabin Repository].

I also agree with Kevin. This is not something that should be done on a regular basis. I can see it as a one off due to extraordinary operations, such as a major archiving of data to another database.