A couple of things you should look at and resolve, but that aren't related to your issues

2009-04-17 04:40:03.09 spid5s SQL Trace ID 1 was started by login "sa".

2009-04-17 04:40:03.11 spid5s...

Sorry, your initial post indicated you wanted user access information, not filegrowth data

In the SQL Error log does it give you any further information? Or the Windows System log that should give an indication of who stopped the service.

Take a look in SYS.Databases , everything you need to know is in there.

matt stockham (4/15/2009)

---

Your final solution will also depend on what you are trying to protect against, what downtime tolerance you have, and where the backup server(s) will be located. ...

That error is generally attributed to a timeout. This could be the application timing out waiting for results or potentially an MDAC issue, check out http://support.microsoft.com/default.aspx?scid=kb;en-us;872968

We have a similar problem with ARSystem as you do with NeverFail. When a failover happened the connection would obviously be lost, and ARSystem isn't smart enough to try and...

Windows 2000 support ended 4 years ago.

SQL Server 2000 support ended last year.

You can find a list of Microsoft products and their support lifecycle at http://support.microsoft.com/lifecycle/?p1=2852

Performance aside you should seriously consider moving on to a supported version of the OS.

If you're on SQL 2005 you could use the NVARCHAR(MAX) datatype instead

I've looked through those links, they were part of the heck knows how many pages I trawled through trying to find an answer. There were a couple of things that...

This is frequently due to SPN problems related to not having the required permissions in AD.

And all the instances are on other servers than the one that you are trying to patch?

Is this in a majority node cluster?

Ouch.

Did you have any problems with any of the other Cumulative Updates?

Yeah, sorry, was trying to change the code I...