check the execution account of the maintenance plan? is it running as the agent account or do you have it running under a proxy. from there you should...

does the user exist as a server principle already? if not it will need to be added as a login first before it can be added as a DB...

declare a parameter or a variable within the report, set it to an expression of the GETDATE() equivilent in SSRS, then use that instead of System.DateTime

thats due to you using the system date time and that is always changing due to it being the system clock. you would need to use a static starting...

what is your expression to work out the start time and end time based on the execution time field?

use the execution time builtin field which is in the report data toolbox of BIDS or report builder.

to get the time in hh:mm:ss you will need to do a variable...

look at the executionlog view in the reportserver database joined to the catalog table on the report guids to get the names of the reports.

Brandie Tarvin (5/11/2012)

---

I find it amusing that this is the only time that having multiple points of failure is a good thing.

Of course, I'm not really sure you should have...

should be a good starting point

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

the related tasks go into how to setup and configure the loop

what level of rights does the account have which is backing up the database?

restricted user only allows members of sysadmin/dbcreator/db_owner roles to connect to the database, so if the account...

no the only way to store a date in any other format than yyyy-mm-ddThh:mm:ss.ms is to store it as a string based data type, otherwise it is convert it...

there was an article posted this week in relation to RegEx for DBA's, it can be found here[/url]

The datetime datatype only stores values in yyyy-mm-ddThh:mm:ss.ms format. I would leave it as this and do the formatting into dd/mm/yyyy in the application or in the calling stored...

vinu512 (5/11/2012)

---

anthony.green (5/11/2012)

---

this will do the job with the sample data provided, but if you dont know the logic then we can only guess at what you want and how...

switch on remote errors then run the report again, this will give you a more detailed error