thank you kind sir

actually it was purely from a poor schema design viewpoint i.e column names which have reserved words and then if you need to call them in a delimited string etc

one...

sorry yes phrased rather badly ... the current amount of free page space

I hang my head in shame

thank you very much Gail !

ahhh we frequently turn them on /off on dev enviornments to shoe horn data in ... just want to add some automatic checks to ensure we turn them back...

I trust you... you like babylon 5 !

but yes I did run a trace with those events selected and it causes a cachemiss so guessing the whitepaper is slighlty out...

so the assertion that it does in the paper is incorrect or am I reading it wrong to start with ? 🙂

http://msdn.microsoft.com/en-us/library/ee343986%28v=sql.100%29.aspx

if you go to the section

Recompilations due to SET option changes

and Im tracing

SP:Starting

SP:StmtStarting

SP:Recompile

...

so based on all your feedback Ive slightly altered Michael's script and I now have :

SET NOCOUNT ON

DECLARE @DBsysname,

@Namevarchar(100),

@Recoveryvarchar(100),

@SQLvarchar(MAX)

SET @SQL = ''

DECLARE db_cur CURSOR FOR

SELECT name

FROM master.sys.databases

wherename like '%cust%'

order...

thank you Gail 🙂

that looks just the ticket with its nested cursor to work out the logfile names

I've added the caveat that "file_id = 2" and will have a further play...

yep just dev/test servers and log space can run away with itself .. not a "real" one 🙂

many thanks Paul ... god I was making life complicated with my code...

~simon

thank you all for your help

Paul thats great I'll go for that appraoch ... far simpler !

~simon 🙂

as for why I was trying to avoid dymanic sql it was due to the potential for performance hits etc