figured it out

MetaData.value('declare namespace NS="http://core.company.com/MetaData.xsd"; (/NS:MetaData/NS:StateStandard)[1]','NVARCHAR(MAX)')

just one thing that I am not so sure on and might cause an issue

when you change from Simple to Full, before you can take a TX log backup...

from what I remember when I was looking at this

you need to look at the authentication methods needed for SSRS, will need custom or forms auth based, then you just...

load the log into a temp table then do a query against the date column

create table @errorlog (date, source, message)

insert into @errorlog exec sp_readerrorlog

select * from @errorlog where date >=...

windows firewall configured correctly?

corporate firewall configured correctly?

any antivirus disabled from blocking massmail worms and the dbmail executable?

server been granted the right to send mails via SMTP?

authentication issues resolved for logging...

or if you want the keyboard shortcut use CTRL+T

two ways

you will either need to create a new job which has a cmdexec step and pass in the script, then modify the job which is created from the maintenance...

most excellent, this has been book marked and a copy of the zip uploaded to my drop box so I dont forget about it.

why dont you add the script as a step in the job after the backups have completed, that way the sql agent runs the script for you

you could use tools like robocopy, xcopy, SAN replication (if you use a SAN) to copy files between locations which will save you backing up twice

happy to help

Change the DBName in the temp table to a data type of SYSNAME this will then eliminate this error from happening.

what is the largest name of a database on the instance?

on first glance it looks that you have a DB name larger than 25 and its failing inserting into the...

something like this

declare @maxseqid int = 101,@count int, @sum decimal (10,2) = 0, @loop int = 1

select @count = COUNT(*) from seq

while @loop <= @count

begin

select @sum = @sum + amount...

if you have connected over VPN then your acting like your on your companies LAN so there is no issue with connecting to SSRS using your normal windows accounts

but when...