Your full database restore should ahve been with norecovery clause i hope you have missed that and the database has already become online. You need to redo the restoration of...

I dont find any issues with that unless and other wise you use the logical name in any of your application programs. you can continue to rename the logical file...

Data would have come from the cache memory of the database server. Once you restarted the service the cache has got flushed and your database was amrked suspect.

Run dbcc sqlperf(logspace) to check what is the space being used by the log file of tempdb

then

backup log tempdb with truncate_only

go

dbcc shrinkfile(2,100)

Also check if any process is running that...

Your database server doesnot use more than 26GB of memory. If you want try monitoring the memory usage with Total server memory and target server memory counters.

You can't do this in SQL server. You are expecting something equivalent to ORACLE package which is not available in sql. The best option would be to create a batch...

I use a few scripts myself to check these things. I check for the server disk space details, services, database status, jobs and thier status etc. This was done with...

Your select @@version command will give you those details.

Ok Brandie no issues. I too learnt few things in this post.

Is the TCP protocol correctly set. Try using named pipes to create the DSN instead of TCP.

I see no known problems. Yu can install 2000 without any issues.

What account does your sql server agent service run. It shoule run under a network service or domain account to access network resources.

You need not need a cursor to do this for you in sql 2005. You have row_number() function in sql 2005 to do this.

Read more on that in link

SQL Server uses “superlatches” in 32-processor configurations. These superlatches reduce the use of Page latches, which in turn reduces resource contention.

This was from a website.

Yes found the answer. The NetBIOS name for any computer can be only 15 bytes and in your case it was 16 bytes and the last character has been truncated....