thanks Perry I thought you would have relevant links to hand.

but i still get my point 🙂

thanks for feeding back, so many people just don't bother.

perhaps this cluster is the first with mount points?

it sounds like SQL is starting before that drive is accessible, are your dependencies correct?

in the log directory created by SQL under your chosen installation path

its all part of the same service pack so yes it will

glad to help, thanks for the feedback

I just cribbed this from a job I run so amend to your needs, but it backups any databases with no backups

create PROCEDURE [dbo].[usp_FirsttimeBkUp]

AS

set nocount on

declare @dbase_name sysname,

@dbase_dbid int,

@SQLString...

only by scripting up exactly what you want to do.

nope, logical and physical names are a one to one relationship

I would expect space in the ldf file to be reused so it should not grow. But no harm to have the figures as evidence to confirm growth or not.

447 MB does not tally with your previous information about log activity.

is it the ldf or trn file that is growing?

Scan the default traces for log growth, you can sort...

I see Redgate have discontinued Hyperbac after buying it up a while back. darn shame.

how big are the log backups? Any of about 30GB hence leading to the log file growth?

If you right click the database, select reports,standard reports,disk usage you can see if...

what does the query

select log_reuse_wait_desc from sys.databases where name = 'your database'

return,

that will tell you what is preventing your log from truncating

this query reverse engineers the sql for the role memberships so alter as necessary, but it returns all role memberships

SELECT 'EXEC sp_addrolemember [' + dp.name + '], [' + USER_NAME(drm.member_principal_id)...