It used to matter but now I see a wider role as a chance to broaden my opportunities with my current(and future) employer(s) and raise my marketability and earning potential.

Drink Heavily 😉

thx. i didn't mean to imply that...

are you saying that your application id has sysadmin role ?

:Whistling:

you can setup a ddl trigger in 2005 to limit ddl activities.

if you're stuck in a pre 2005 world you would do:

select * from sysobjects where type ='u'

and name like '%your_table_name%'

consider running a profiler trace to see if you have queries consuming

excessive resources. look for high duration and/or reads values.

all it takes is 1 missing index.

on that note...do you have...

sp_delete_backuphistory

i wonder if you could create a proc that kicks off at startup that increments a

counter in a table somewhere.

if the servers down......no incrementing happens.

if its up....well...you get the picture.

if you're not cleaning it up then i think yes.

select min(backup_finish_date) from backupset

how much you keep depends upon your needs and system's ability to handle it.

i keep a year and...

also run these in your msdb:

select 'sysjobhistory', count(*) from sysjobhistory with (nolock)

select 'sysjobs', count(*) from sysjobs with (nolock)

select 'sysjobactivity', count(*) from sysjobactivity with (nolock)

select 'sysjobsteps', count(*) from sysjobsteps with (nolock)

select...

that depends on whether or not you need the history.

that doesn't seem like a lot with the few job you have.

run a trace to see whats going on. see where...

how long...

running the above command will help you determine whether any database(s) have

been created on your F: drive

no. you should not need to reindex.

you also should not need to reindex after a restore.

(unless the indexes in your backup are fragmented)

msdb also stores your backup history among other things.

are you doing anything to purge backup history ?