Viewing 15 posts - 61 through 75 (of 108 total)
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
October 14, 2005 at 12:47 am
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 you can...
June 29, 2005 at 10:41 am
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 schedule as...
June 29, 2005 at 8:04 am
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 schedule as...
June 29, 2005 at 12:44 am
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 possible to...
June 24, 2005 at 1:54 am
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?...
June 3, 2005 at 3:13 pm
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...
June 3, 2005 at 7:12 am
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 lot of...
June 3, 2005 at 12:46 am
PS:
Sorry all the indents and formatting got wasted in the post here.
June 3, 2005 at 12:36 am
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).
...
June 3, 2005 at 12:35 am
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 relationships.
Run...
May 31, 2005 at 11:36 pm
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',
...
May 23, 2005 at 8:52 am
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...
May 19, 2005 at 12:01 am
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.
...
May 17, 2005 at 12:30 am
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 http://codetempest.com/node/10...
May 17, 2005 at 12:22 am
Viewing 15 posts - 61 through 75 (of 108 total)