well, shrinking the log can be acheived by using DBCC SHRINKFILE(logfilename, size). (depending upon how much space is currently being used, you will be able to shrink it to any...

DECLARE @vcCmdVARCHAR(666)

CREATE TABLE #tbl_Backups

(

BackupNameVARCHAR(200)

)

--assumes that the latest file was put in last. (order by files newest file first)

SET @vcCmd = 'DIR "J:\Microsoft SQL Server\MSSQL.1\MSSQL\backup\WebData\*.bak" /b /o-d'

INSERT INTO #tbl_Backups

EXEC xp_cmdshell @vcCmd

DELETE...

/*

Hi nailosuper,

your question is a bit vague? you would like to tell if your log files are too big? one of the first things that you need to work out...

/*

Hi Mike,

this can be quite a mission to get right.

by changing the database collation you are not changing the collation of the columns or tables that have been explicitly...

/*

you actually have quite a few options. I would probably do something like this: (as it seems that you do not have linked servers) note: you will need to run...

/* well, this will work, though it is a little elaborate. it does however provide some other cool info about the processer(s)*/

DECLARE

@nProcessorCountINT

,@vcProcessorModelVARCHAR(5)

,@vcProcessorTypeVARCHAR(30)

,@vcProcessorNameStringVARCHAR(60)

CREATE TABLE #tblStats

(

[Index] INT,

[Name] VARCHAR(200),

Internal_Value VARCHAR(50),

Character_Value VARCHAR(200)

)

INSERT...