What is the actual version of each instance where this occurs? It could be a bug in the maintenance plan task - where it only performs the backup task...

I would recommend that you stop using backup devices - setup the maintenance plan or your backup scripts to use a separate file for every backup.

Evil Kraig F (9/21/2012)

---

JanTimmermans (9/21/2012)

---

But I'm still curious how you'd rewrite the procedure without using an cursor 🙂

What we do:

Select ID, Adress, Zipcode

From aTable

Open Cursor

Fetch Next into variables

Do while eof

...

If the current process is backing up to a single file - at what point is that file initialized? Because, once initialized - all previous log backups are gone.

If...

It could be related to when the Y:\ drive is actually becoming available. If that was never set as a dependency before - and it was coming up before...

And that would be your problem - without the dependencies, SQL Server cannot see the drive. Since SQL Server cannot see the drive - it cannot be started.

Does the SQL Server cluster resource have a dependency on the Y:\ drive?

Because that is not a hard-coded date. It...

HEAP's cannot be rebuilt - they will always show fragmentation.

As for the other indexes, how many pages in the index? What are the data types for the indexes? ...

In addition to what Grant stated - there is a utility called SQL Server Configuration Manager. Open that and you can see all of the services available for SQL...

jrichards54 (9/14/2012)

---

You wrote: "You cannot install SQL Server Service Packs until SQL Server itself is installed." and I ask then why did the Install ask for the SP3 to be...

Add another criteria to the where statement in the second pipeline:

Get-ChildItem C:\SSISFILES\Log -Recurse | Where {!$_.PsIsContainer -and $_.LastWriteTime -lt (Get-Date).AddDays(-5) -and $_.Extension -eq ".txt"} | Remove-Item -Force -WhatIf

Okay - you need to install SQL Server first. When you get the compatibility warning - continue the install. Once that has finished, then you can apply the...

Instead of using cmd exec - use Powershell with the following:

Get-ChildItem C:\SSISFILES\Log | Where {$_.LastWriteTime -lt (Get-Date).AddDays(-5)} | Remove-Item -Force

If you want this to recurse through sub-directories and delete files,...

You don't need to worry about SP3 - just download and install SP4. They are cumulative so you will be fine with that.

The reason you are getting the notice...