I would not rebuild/reorganize the indexes during business hours unless the fragmentation itself it causing a high severity incident.

Like mentioned earlier, if the DNS points to the new IP, SQL Server name need not be changed.

I am no expert on DNS. It can be an option. If you change the DNS to point to the new IP, the server name remains the same. Hence there...

First rename that computer. That would take care of everything like AD/DNS etc. After that you can rename the other computer.

Please go through this article.

This error has nothing to do with the configuration of the instance.

The data file has corruption in it. Please look out for the last good backup for this database. Also...

Like I said earlier, till one has access to the folder no file can be copied including backup files. There is no way to do it

If a computer name already exists on the network, it will not allow you to change the computer name. If you run into any problems after changing the server name,...

Hi,

Take the backup of the Public Network database locally on that server. Then you can move it your local drive. Unless you have access to the path where backup is...

Is this a dedicated server for SQL Server? If yes then the max memory is set too low (3500 MB out of 8192 MB). I would leave 2 GB...

You can make use of Profiler, perfmon among others to track High CPU utilization issue. You may find this article useful.

Please go through this article which has lot of options on how to fix this error.

I doubt this error has to do anything with Max Worker Thread option. The error Error: 18456, Severity: 14, State: 27 means SQL Server could not determine the initial database...

Is the process still running and you are unable to kill it?

I have not come across a situation where the SPID is valid and I am unable to kill it.

Please go through this[/url] useful article on SSC.