July 9, 2008 06:59am pdt

1. chapmandew 1,545,836
2. angelIII 1,231,150
3. aneeshat... 517,561
4. mark_wills 415,981
5. ee_rlee 348,824
6. ScottPle... 287,651
7. dtodd 272,301
8. acperkins 190,773
9. Thomasian 151,038
10. cs97jjm3 135,235
11. matthews... 131,903
12. EugeneZ 128,009
13. ptjcb 119,637
14. appari 113,498
15. dbaSQL 112,669

1. angelIII 10,187,563
2. aneeshat... 4,575,440
3. acperkins 4,179,233
4. ScottPle... 4,101,703
5. arbert 2,245,195
6. Lowfatsp... 2,165,176
7. chapmandew 1,545,836
8. rafrancisco 1,460,132
9. imran_fast 1,458,588
10. EugeneZ 1,404,171
11. Hilaire 1,221,775
12. Nightman 1,143,404
13. Mr_Peerapol 1,087,815
14. nmcdermaid 1,060,022
15. ptjcb 1,053,496

04.24.2008 at 06:09AM PDT, ID: 23350095

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.3

Setting a trigger in Sql 200 to shrink a log file

Zone: MS SQL Server

Does anyone have a neat little sql syntax, which will kick of a stored procedure or job to shrink a log file if it exceeds a certain limit?

Start your free trial to view this solution

Question Stats

Zone: Microsoft

Question Asked By: kpwhitte

Solution Provided By: chapmandew

Participating Experts: 2

Solution Grade: A

Translate:

Loading Advertisement...

Microsoft

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Apple

Operating Systems
Hardware

Programming
Networking

Software

Internet

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Gamers

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Digital Living

Hardware
New Net Users
New Users

Software
Digital Music
Gaming World

Home Security
Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Hardware

Handhelds / PDAs
Displays / Monitors
Components
Networking Hardware

Peripherals
Laptops/Notebooks
Storage
Servers

Desktops
New Users
Misc
Apple

Software

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMWare
Misc
Web Development

OS
CYGWIN
Voice Recognition
Message Queue
Quality Assurance
Security
Firewalls
MultiMedia Applications

Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

ITPro

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals

Devices
Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
WebApplications
IDS
Vulnerabilities
Email Clients

File Sharing
Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Chat / IM
Anti Spam

Developer

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Storage

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMWare

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Database

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Security

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Programming

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel

Algorithms
Game
Signal Processing
Project Management
Open Source

Database
Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Images

Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration
WebApplications

Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Networking

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Broadband

Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Other

Community Advisor
Lounge
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles

Community Support

Suggestions
New to EE
New Topics
Community Advisor

CleanUp
Announcements
General

Feedback
Input
EE Bugs

04.24.2008 at 06:16AM PDT, ID: 21430430

Rank: Genius

chapmandew:

           IF EXISTS(
SELECT CAST(((SIZE * 8.00)/1024.00) AS DECIMAL(18,2)), *
from sys.database_files
WHERE
                  type_desc = 'LOG' AND
                  CAST(((SIZE * 8.00)/1024.00) AS DECIMAL(18,2)) > 5000 --5 GB
            )
            truncate log yourdbname with truncate_only

            dbcc shrinkfile('your log file name',0)

04.24.2008 at 06:18AM PDT, ID: 21430457

Rank: Genius

chapmandew:

the above code runs in a certain database, looks to see if the log file is over 5gb. If it is, then it truncates the log file and then shrinks it. Becareful with the code, but it should take care of what you need.

If you want to put it in a proc:

create procedure myproc
as
IF EXISTS(
SELECT CAST(((SIZE * 8.00)/1024.00) AS DECIMAL(18,2)), *
from sys.database_files
WHERE
type_desc = 'LOG' AND
CAST(((SIZE * 8.00)/1024.00) AS DECIMAL(18,2)) > 5000 --5 GB
)
truncate log yourdbname with truncate_only

dbcc shrinkfile('your log file name',0)

04.24.2008 at 07:00AM PDT, ID: 21430896

kpwhitte:

should the code just be put into a sp or job, or kicked off with a trigger?

04.24.2008 at 07:03AM PDT, ID: 21430928

kpwhitte:

here is the syntax I am using now. Just running it out of sql analyzer; however, it is not "dynamic".

USE Taske;
GO
ALTER DATABASE Taske
SET RECOVERY SIMPLE;
GO
DBCC SHRINKFILE (Taske_Log, 200);
GO
ALTER DATABASE Taske
SET RECOVERY FULL;
GO

04.24.2008 at 07:16AM PDT, ID: 21431066

Rank: Genius

chapmandew:

try this:

create procedure usp_ShrinkDB
(
@DBName nvarchar(255)
)
AS
BEGIN
      DECLARE @SQL NVARCHAR(4000)
      SET @SQL = 'ALTER DATABASE ' + @DBName + 'SET RECOVERY SIMPLE'
      EXECUTE sp_ExecuteSQL @SQL
      SET @SQL = 'DBCC SHRINKFILE (' + @DBName + '_Log, 200)'
      EXECUTE sp_ExecuteSQL @SQL
      SET @SQL = 'ALTER DATABASE ' + @DBName + 'SET RECOVERY FULL'
      EXECUTE sp_ExecuteSQL @SQL
END

04.24.2008 at 07:16AM PDT, ID: 21431072

Rank: Genius

chapmandew:

I would put it in a job.

04.24.2008 at 08:48AM PDT, ID: 21432179

kpwhitte:

it is not clear to me how this code shrinks one particular database file. sorry for my ignorance.

04.24.2008 at 08:51AM PDT, ID: 21432209

Rank: Genius

chapmandew:

so, you pass the name of the database into it that you want to shrink....it then shrinks the log file for the database....exact same code you posted, but dynamic so that you can pass it a db name.

04.24.2008 at 09:34AM PDT, ID: 21432694

kpwhitte:

where does the name get passed from?

thanks

04.24.2008 at 09:53AM PDT, ID: 21432871

Rank: Genius

chapmandew:

Its a procedure, so you'd have to pass it in when calling it....

execute usp_ShrinkDB 'mydbname'

04.24.2008 at 02:21PM PDT, ID: 21435253

kpwhitte:

passing the parameter fine now, but receiving the following message

[Line 1: Incorrect syntax near 'SIMPLE'. [SQLSTATE 42000] (Error 170) Associated statement is not prepared [SQLSTATE HY007] (Error 0) DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Message 2528) Incorrect syntax near the keyword 'FULL'. [SQLSTATE 42000] (Error 156). The step failed.

04.24.2008 at 03:02PM PDT, ID: 21435582

Rank: Genius

chapmandew:

lets change it a bit...you don't need to change the recovery options to do this:

DECLARE @SQL NVARCHAR(4000)
SET @SQL = 'BACKUP LOG ' + @DBNAME + ' WITH TRUNCATE_ONLY'
EXECUTE sp_ExecuteSQL @SQL
SET @SQL = 'DBCC SHRINKFILE (' + @DBName + '_Log, 200)'
EXECUTE sp_ExecuteSQL @SQL

Accepted Solution

04.24.2008 at 03:25PM PDT, ID: 21435727

Rank: Savant

angelIII:

note:
you should NOT be trying to automatically doing a shrink log file.
either, your database is in simple recovery mode, then the file should keep a constant size after short time, do not try to shrink it
or your database is in ful recovery mode, then you should implement a regular (full and) transation log backup, which will make the tlog file reuse the space allocated.

Assisted Solution

20080236-EE-VQP-29 / EE_QW_2_20070628