You are right. "Not enough storage is available to process this command" error indicates that there is insufficient memory for that query to execute. Please check which process in SQL...

@msn29,

Does the backup task has "Create a sub directory for every database" option selected? If yes, then the "Include first-level subfolders" option needs to be selected in Maintenance Cleanup Task

As far as I know they cannot be separated.

I second Jason. What is the error message with which the KB installation is failing? You can find the details in SetupBootStrap\Logs folder.

Since C2 audit trace files are created on the default data directory for SQL Server, you may change the Default Data directory

Here is an example. Create a new batch file say loadtest.bat which has the following code in it

sqlcmd -SServerName -E -Q "sp_who2"

loadtest.bat

This will run sp_who2 continuously until you stop...

Do you see any error messages in SQL Server Error Log\ Event Log?

Yes. Most likely you would have entered .BAK. This is one of the changes in SQL Server 2005 from SQL Server 2000

You may have a look at Reporting Services Scripter

Muhammad, glad to know that it worked 🙂

Easy way out is script to script the profiler trace and run it on the instance. You may find this[/url] useful.

Yes. The only way to get rid of 3013 error is to delete the existing backup file or taking the backup in a new directory

Even if you drop the login, some application is trying to connect to this instance from 172.18.3.7. The only option to figure out is to check with the support team...

SQL_Latin1_General_CP1_CI_AS is the default collation for SQL Server 2008. Not sure how it is termed as "for backward compatibility"

SQL Server 32 bit cannot be upgraded to 64 bit. It needs to be reinstalled. This whitepaper explains the benefits of 64 bit architecture.