Steve,

I'm glad you liked the article.  Sure, I could write an article on this. However, I am very bad in that I am pulling data from system tables.  Maybe I can...

Maybe you are trying to find Query Analyzer?  You can find it in the SQL Server group in Programs or in Enterprise Manager by looking in the Tools menu.   

In Query...

Hmmm, does that work across servers?  I would think you would have to create a linked server to accomplish that.

There is a stored proc in MSDB called sp_Help_MaintenancePlan, but it doesn't look real helpful.  The query below gives information about the maintenance plans, but not the schedules:

SELECT  sj.job_id,smp.plan_name, substring(sj.command,80,100)as...

Instead of the Select '''', try using Print '''' . It worked for me!

You probably have multiple rows in table1 that match a given row in table2. 

Take a look at the COMMAND object found in ADO and ADO.NET. 

A database can be set to one of three recovery models: Full, Bulk-Logged and Simple.  The system databases are set to Simple. When a database recovery model is set to...

Here's an article that may give the answer you are looking for: http://www.microsoft.com/technet/prodtechnol/sql/2000/reskit/part10/c3761.mspx

It describes using INSTEAD OF triggers to allow updates to multiple tables through a view.

Do you mean parameters?  If so, you could do something like this:

create proc usp_Test @myParam int as

   if @myParam <= 5 begin

      raiserror('Param must be over 5',11,1)

      return

  end

  --...

SQL 2000 BOL says that you can only create INSTEAD OF triggers on views and then only if the view was created without the WITH CHECK option.  INSTEAD OF triggers...

I was really aggravated when hired on as a VB consultant and all in-house programs and utilities had hard-coded IP addresses and file paths in the VB executables.  I remember saying...

I would filter on the database ID instead. You can get that from sp_helpdb.  I haven't ever gotten profiler to filter properly on the database name.

While SQL Server Agent is stopped, delete the file. When you start up SQL Agent again, it will create a new blank file. By default it should be called SQLAGENT.OUT...