To confirm, if you try to access SSRS via the web instead of your C# app, HTTPS is working correct? I would make sure that it is working from the...

With the new job, did you use the same start date? If so, may not hurt to bump the new start date up to the next expected run date.

Another question for you then - is it consistently FAST and SLOW if you run the same query in SSMS and the ERP OR is it only fast/slow in the...

So that is based on your start date. Jan 1st, 2015 + 26 months is March 1st, 2017. Next run is May 1st, 2019, then July 1st, 2021, then September...

• This reply was modified 10 months, 2 weeks ago by  Mr. Brian Gale. Reason: better solution provided by another poster

Are you really using SSRS 2005 or 2008? If so, I would recommend upgrading to a supported platform.

But, I wouldn't recommend adjusting the files manually when there is a GUI...

To add to what Grant said, are you using this in a stored procedure and passing that B700 and C900 as parameters? If so, then this could be a parameter...

Have you tried deleting the schedule and making a new one?

I've had schedules not behave the way I want (usually after doing in-place upgrades) and deleting the schedule and recreating...

Are you able to switch to simple recovery mode and do a backup? If so, that should put your log file down to 99% unused at which point you should...

Maybe I am a bit ignorant here, but can't Excel save as CSV? Do you really need an SSIS package to convert an Excel file to CSV?

Failing that, powershell can...

My understanding is this is often done for performance purposes. If you are on spinning disk (HDD) and the MDF + NDF are on the same disk, then the benefits...

To me it looks like your Antivirus thinks the installer is infected. If you are 100% confident that the installer is NOT infected (ie you got it from Microsoft and...

My opinion - predicting log file usage is tricky and often not a good use of resources (your time and energy). I've seen systems that have 0 transactions one hour...

Just to play devil's advocate here - be careful adding indexes. Each new index causes some data duplication on disk. So the more indexes you have, the slower your DML...

Quick guess - this is a stored procedure? If so, then the change in plan is due to change in parameters. It kind of looks like a parameter sniffing problem....

Just wanted to add in that the "working 8-4" thing is something that only happened recently as my work contract got changed. At one point, I was on call 24/7/365...