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...

A nice read for a Saturday morning. I remember back when I started in my current department and I thought "one day, I want to be a manager like my...

What you could do then is change your SQL to include a TOP(1) and an order by FailDate DESC. Will that solve your issue?

Alternately, make your whole query a subquery...

I think the easiest way to help you is if you can:

1- provide sample data so we can run your query and get similar results

2- provide expected output

With point number...

In that case, what you are likely more interested in is the page life expectancy. How long are pages estimated to remain in memory:

https://www.sqlshack.com/page-life-expectancy-ple-in-sql-server/

The lower the number, the more memory...