I agree, but I don't think the programmer will buy it.  I just want him to understand why.  If I find a good article, I'll post it.

Maybe I don't understand your question, but your users can continue to use Query Analyzer to connect to SQL 2005 databases.  You can also connect to them with other query tools like...

It might have something to do with SharePoint installing as the default web site.  We got a similar error on a test box here (sorry, don't recall what it was)...

I'm guessing that neither server has a service pack on it, so maybe that information will appear later.  Thanks.

I've looked at 2 different servers (one a Windows 2000, the other 2003) and see no Reporting Services version numbers on the home page anywhere.  Where specifically do you see...

Actually, I agree with letting the developers have Management Studio as well.  Since SQL 2005 has a greater granularity level of security, I'd rather they have it than Enterprise Manager. ...

All I do is run sp_who2 and search for one of the two node names.

I just installed SQL 2005 service pack 1 on a test box and the errors went away.  I'm going to install it on a production box soon--hopefully the errors will go...

We have an older database server that was built on RAID 5 that is getting the same type of I/O errors during database backups.  This server isn't particularly critical so...

Once you restore the primary you will need to set up log shipping all over again.  Sorry, but here is no way around it.

I'm not sure about the hardware but I'll look into it.  If the DROPCLEANBUFFERS is a "performance killer" I hesitate to run it on this particular server.  Do you recall...

No.  The information you just mentioned is kept in msdb and master.  All you would be restoring is the user database.

As an alternative, why don't you backup the database and restore it WITH NORECOVERY on the second server?  Then you can set up log shipping.  I've never had a problem doing it...

First things first...  I hope you have good backups.  Your information is a bit schetchy--do you still have the master.mdf & .ldf (and model and msdb) or are those gone...

From what I can tell, it is the pointer (or information file) that tells log shipping where it left off with its last restore.  We log ship throughout the day,...