Profiler [SQL Timeout using perfmon.msc]

After reading the information on the Poor man's monitor
http://www.sqlmag.com/Articles/ArticleID/37468/pg/2/2.html I began to believe
I could write an application that would immediately tell me when a timeout
was happening. Being that the server is a production server, I don't dare
test on it and the testing I did indicated that only the Server 2003 was able
to pull the data I was looking for (as the article indicated).
The problem is that when I set up the profmon.msc on the 2003 server to look
at the SQL timeouts on the 2000 server, it brings back nulls to the three
monitoring tables Counterdata, CounterDataDetails, and DisplayToID.
Is there a way to coax the actual SQL Lock Timeout data back from the 2000
server to the 2003 server through PerfMon.msc?
Should I post this to a different user group?
--
Regards,
JamieAnswered my own question. The counterid will increment each time the table
is created. I believe my smallest counterid in the counterdetails was 191.
When I reset the query to point to the right counterid, it immediately
produced results.
--
Regards,
Jamie
"thejamie" wrote:
> After reading the information on the Poor man's monitor
> http://www.sqlmag.com/Articles/ArticleID/37468/pg/2/2.html I began to believe
> I could write an application that would immediately tell me when a timeout
> was happening. Being that the server is a production server, I don't dare
> test on it and the testing I did indicated that only the Server 2003 was able
> to pull the data I was looking for (as the article indicated).
> The problem is that when I set up the profmon.msc on the 2003 server to look
> at the SQL timeouts on the 2000 server, it brings back nulls to the three
> monitoring tables Counterdata, CounterDataDetails, and DisplayToID.
> Is there a way to coax the actual SQL Lock Timeout data back from the 2000
> server to the 2003 server through PerfMon.msc?
> Should I post this to a different user group?
> --
> Regards,
> Jamie

ProcessRowInput not containing any Row data

I have a script component as a destination. I believe I'm doing something very simple, but for some reason, I'm not getting back any data.

When I just msgbox the data in Row.Address, I get nothing. If I msgbox Row.Address.toString, I get "Object reference not set to instance of an object."

Public Overrides Sub Input0_ProcessInputRow(ByVal Row As Input0Buffer)
MessageBox.Show(Row.Address)
End Sub

I have Address as an input and output column in my script component setup. Any help? It seems like it's gotta be something simple, but I'm pulling my (little bit of) hair out to find it.

mmmm... think my problem is elsewhere. thanks anyways!

Processing of AS2005 cube from Integration Services package: Operation completed with 882 proble

Hi!

I did not now if I should post it in the Integration Services forum, but I believe this post is more AS related. Anyway, I am processing my cubes in SSIS after some loading of data. I use the SSIS log provider for SQL Server to log errors, and I get the following error message in the message column of a row in sysdtslog90:

"Server: Operation completed with 882 problems logged."

I wonder, where can I find this log? Is there some default location in AS or do I have to enable another log event than OnError or OnWarning in SSIS?

Thanks!

I'm guessing I'm looking for the Dimension key error log path when it is set for (default).

I found something here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1284202&SiteID=1

Seems like you have to set the location in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Config\msmdsrv.ini. Now I get a key error logfile, but it is empty =/. I've restarted the AS service and set the ErrorLog elements in the ini to:

<ErrorLog>
<ErrorLogFileName>OLAPErrorLog.log</ErrorLogFileName>
<ErrorLogFileSize>4</ErrorLogFileSize>
<KeyErrorAction>0</KeyErrorAction>
<KeyErrorLogFile>KeyErrorLogFile.log</KeyErrorLogFile>
<KeyErrorLimit>0</KeyErrorLimit>
<KeyErrorLimitAction>0</KeyErrorLimitAction>
<LogErrorTypes>
<KeyNotFound>1</KeyNotFound>
<KeyDuplicate>0</KeyDuplicate>
<NullKeyConvertedToUnknown>0</NullKeyConvertedToUnknown>
<NullKeyNotAllowed>1</NullKeyNotAllowed>
</LogErrorTypes>
<IgnoreDataTruncation>0</IgnoreDataTruncation>
</ErrorLog>

I've also tested the following without success:

<ErrorLog>
<ErrorLogFileName>OLAPErrorLog.log</ErrorLogFileName>
<ErrorLogFileSize>4000000</ErrorLogFileSize>
<KeyErrorAction>1</KeyErrorAction>
<KeyErrorLogFile>KeyErrorLogFile.log</KeyErrorLogFile>
<KeyErrorLimit>1</KeyErrorLimit>
<KeyErrorLimitAction>1</KeyErrorLimitAction>
<LogErrorTypes>
<KeyNotFound>1</KeyNotFound>
<KeyDuplicate>1</KeyDuplicate>
<NullKeyConvertedToUnknown>1</NullKeyConvertedToUnknown>
<NullKeyNotAllowed>1</NullKeyNotAllowed>
</LogErrorTypes>
<IgnoreDataTruncation>0</IgnoreDataTruncation>
</ErrorLog>

More info here, but it does not get you that much wiser: http://technet.microsoft.com/en-us/library/ms174827.aspx

Seems like you do have to set the ErrorLog properties manually for each cube (Process > Change Settings > Use custom error configuration).