No you don't need to reinstall the server.

See here:

http://msdn.microsoft.com/en-us/library/dd207004.aspx

You could probably just use the If..else logic already built into your procedure to do this.

So declare the alternative ALTER statement at the top of the query, something like this..

DECLARE...

It looks like your command is getting truncated so the opening quotation mark never gets terminated.

You could declare @command as varchar(max) but unfortunately in this case I don't think it...

If this was an in-place upgrade you'd expect the jobs and maintenance plans to be preserved, obviously they'd be lost on a clean install.

You might check to see if...

Is the SQL Agent service running? If not, start it up and set it to Automatic.

Find the job that backs up the databases and have a look at it's history,...

The code looks fine anyway.

You may have done this already but I'd start with right-clicking on 'database mail' in SSMS and sending a test email, just to confirm mails are...

If you want to use t-sql you can query msdb..backupset

To see the backup history stored on one database..

select database_name,[type], backup_finish_date

FROM msdb..backupset b

WHERE database_name = 'myDatabaseName'

ORDER BY b.DATABASE_NAME, b.backup_start_date desc

To see...

Something like this might do the trick for you..

SELECT p.name,p.type_desc,r.name as [server role]

FROM

sys.server_principals r

INNER JOIN sys.server_role_members m ON r.principal_id = m.role_principal_id

INNER JOIN sys.server_principals p ON

p.principal_id = m.member_principal_id

order by 1

although...