How about the 'old school' way ...

C:\>copy /?

Copies one or more files to another location.

COPY [/D] [/V] [/N] [/Y | /-Y] [/Z] [/A | /B ] source [/A |...

Lots of questions to answer ...

How are you performing the database backup ?By a maintenance plan ? By a transact SQL statement ? By a third party product ?

Have you...

Here is another link that may be of assistance:

http://support.microsoft.com/kb/828337

If your SQL Servers system event log and application event log do not indicate any type of disk hardware error you are not out of the woods. You could also...

• Does the System Event Log have any network related errors on the SQL Server ?
• Are the NIC cards in your server(s) 'teamed' ?
• Have any firewalls been added ?
• Have any firewall rules...

Jeff's caveat is correct. We have a couple of Binary instances and case sensitivity is definitely something to watch out for.

great article ALZDBA ... I wish there was more information on ...

Of course there are other factors, such as RAID stripe size, RAID controller CPU utilization, controller caches, data file...

Here are a few other applications that have this same issue "big time":

• MOM 2005
• Orion Network Minortoring
• Pathways Compliance Advisor from McKesson

Be wary of 3 tier applciations that utilize connection pooling....

Remembrance, a parade, remembrance, bar-b-que, remembrance, friends, remembrance and family.

I have this problem with our BES from time to time (and a few other applications as well. Many connections, no CPU and no memory allocated just hanging around. Our...

This seems to be a waste of enterprise money. We already implement this architecture with multiple domains and servers of all application types (SQL, AD, Exchange, Web, Application, etc) and...

There is one for 2005 but it is a PDF document .... in my opinion MS blew it for DBA usability and scored on marketing 'fluff' ... here is the...

Here is a handy limk no DBA should be without:

http://www.microsoft.com/sql/prodinfo/previousversions/systables.mspx

I would strongly suggest full database backups of all databases (system and user) and get them off to tape or another server. I say this because if the OS guys screw...

First thing I would try is to reboot the server then examine the System and Application event logs along with the SQL Server errorlog. Next I would take a look...