Check out this link for a good synopsis of how to easily regularly shrink your tranaction log file:

Dynamically Shrink the Transaction Log with a Stored Procedure

http://codetempest.com/article.php?story=20050703191510469

Again, you really should check this out:

"Dynamically shrink the transaction log with a stored procedure"

http://codetempest.com/node/10

It shows you how to create a stored proc in your master database that...

Again:

Check out this link:

"Dynamically shrink the transaction log with a stored procedure"

http://codetempest.com/node/10

It shows you how to create a stored proc in your master database that you can then...

Check out this link:

"Dynamically shrink the transaction log with a stored procedure"

http://codetempest.com/node/10

It shows you how to create a stored proc in your master database that you can then...

Check out this link on SQLServerCentral.com for the sp_who3 procedure:

http://www.sqlservercentral.com/scripts/contributions/1109.asp

... by racosta.

In it s/he creates a temp table and then does this insert:

INSERT INTO #tmp_who2

EXEC sp_who2

So it is...

I don't know. Is that kosher? It has a copyright (c) in the version in the book. Would we have to have Ken Henderson's permission to put it up here?...

Sure, after you create the stored procedure, put put the below in a SQL job and schedule it to run a couple of times a week (on off hours of...

If you have to do a lot of funky replacing and such, I HIGHLY recommend using regular expressions, particularly the PCRE extended ones available at this link.

http://www.codeproject.com/database/xp_pcre.asp

Seems a...

PS:

Sorry all the indents and formatting got wasted in the post here.

Create this in the master database and run it in the offending database. Works in tempdb as well. This proc (sp_trx_log_shrink is for shrinking the log).

...

This should do what you want:

http://www.sqlservercentral.com/scripts/contributions/1035.asp

DO NOT ACCIDENTALLY RUN THIS SCRIPT IN A PRODUCTION DATABASE unless you know what you are doing. It will drop all your FK...

Yes. I use it to script out the entire database. It looks something like this (in a SQL Job that runs nightly):

/******************************************************************************/

EXEC sp_generate_script @outputname='\\MY_OTHER_SVR\DBs_scripted\MyDB_db_script.sql',

...

Using Ken Henderson's sp_generate_script stored procedure (see below)...

Create a SQL Job with 2 steps. This is Step 1. It copies creates as script of the database with the date taged...

How about Yul Wasserman's KillAllProcesses script at http://www.databasejournal.com/scripts/article.php/1491371 ?

CREATE PROCEDURE sp_KillAllProcesses

@dbname varchar (100)=NULL, /*database where we will kill processes.

...

Unless you have some specific need to run the database in full recovery mode, don't. Use bulk logged. This will really cut down un unnecessary db growth.

Also, see