First, let me thank you profusely for the nice article that set my thinking wheels in motion. Great job on that solution!
I have a few questions to clerify why this works the way it does:
1. You're using eventcreate.exe in both SQL2000Blocking.vbs and SQL2005Blocking.vbs. My SQL 2000 is running on Win2K, and instead of eventcreate it has logevent utility. Do your Win2K boxes have eventcreate.exe?
2. Not sure why you're using sql auth to write to AnalysisDb on both SQL 2000 and SQL 2005?
I read that "Again, to avoid giving Local System elevated rights on the SQL instances, access to the central repository database in the vbs scripts had to be done through SQL authentication." But I didn't see DBCC inputbuffer () or fn_get_sql in the stored procedure. Am I missing something?
I think that NT AUTHORITY\SYSTEM account should have write access anyway, so you'd be ok there.
Thanks in advance