What do you want it to contain specifically?

I would honestly recommend that you figure out another way to monitor this. What you have is an incredibly expensive way of doing this, and I wouldn't do it...

Take a look at this thread and see if the information marked as the answer helps you solve this problem:

http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/772834e7-9b96-4e88-bdc5-aebff246bfb4/

It is also dealing with SPN's, but in a different context...

No it shouldn't be. In a multi-instance server, by default the named instances don't have a set port to run on. The port is dynamically determined at run...

GilaMonster (12/18/2008)

Only 2? Be grateful, I've got 11. Only two of those are due to immigration (and...

I always have trouble finding stuff initially online, but nothing is ever written about SQL or .NET in Redneck. I have been talking with Adam Machanic lately by email,...

It's also not cool to post questions without enough meat or content to make them very meaningful. Your interpretation of what might be being asked her is very different...

I have never used a colon except for JDBC, otherwise I use a comma to specify port after the IP.

Are you running the perfcollector local to the x64 server or remotely? I monitor all of my SQL Servers remotely using SQLH2 on a x86 server, and I get...

Are you running multiple instances of SQL Server, and what account is the SQL Service using for the Service Account? If you have multiple instances, it may be possible...

Microsoft recommends that you not apply a cumulative update unless it is specifically addressing a problem you are having. The reason for this is that CU's don't get the...

What version of SQL Server are you on currently? If you are on SQL 2005, a CLR procedure with EXTERNAL ACCESS would be a much more secure method of...

You have to use a doube >> to pipe the results to a file at the command prompt.

Tempdb is in simple recovery so backup log won't help in that case, and if it is the data file and not the log file that is to large backup...

I responded to your post on the MSDN Forums already.