DTS has a transfer jobs task.

And for the DTS packages, I usually backup msdb from the "old" server and then restore it with a different name to the "new" server.  ...

This is not a feature of the SQL Server Tools.  This is more a feature of Windows. You can do this with a whole stack of products.  Try dragging a...

An option to consider is to use a tool such as red-gate's SQL Compare to generate your scripts.  This does a pretty good job. 

We automatically stored all database objects...

A single SQL Server instance is not really aware of other instances running on the same windows server.  I would expect that each of the instances would be able to...

The error you are getting seems to be because the disk system you are using is not able to keep up with the number of I/O requests that are being...

I would be looking harder at the application.  I have never experienced an issue with a SQL thinking that a connection is open if the application has closed it properly. ...

It is time to start believing.  As far as I am aware, the tools supplied with SQL Server do not bother with managing dependency ordering in the manner you are...

SQL Server Clustering requires the disks that are used by SQL to be available to all nodes.  It looks like drives D: and E: might be.  These disks will need...

Good luck.  Hopefully the problem was transient but a little paranoia is advisable.  Make sure that the disk sub-system is stable otherwise you will be playing the same "Restore the...

Did you restart SQL after running sp_resetstatus

Have a look at topic "Resetting the Suspect Status" in Books Online.  It tells you how to change the status of a suspect database. 

Also, have a look at the...

I get this sort of error occassionally.  It usually happens when I add code to debug (e.g. return the results of some intermediate query) that is now returning no records.

Grab...

Check what user owns the SQL Agent Job for the distribution agent.  I have had some issues with the job being owned by a domain login (the person who created...

Autoshrink is the reason that your database  size keeps reverting back to the old settings. 

Personally, I would not set this option on a production server.  It is a better...

The restore process will restore the database as it was when backed up.