The best error handling method in SQL 2000 is defensive programming that checks everything in advance that you can think of that might cause an error.  SQL 2005 gives you...

I don't think I've tried that.  Have you tried setting the agent job step up both as a Integration Services step and as a CmdExec step that uses a dtexec...

One technique would be to add something at the end of the job that inserted a record in a table, updated a record, or otherwise created an artifact that the...

If you have enabled xp_cmdshell, you could use it to execute dtexec to run the package.

If you set up an unscheduled Agent job with one step to run the package,...

You're going to have to dig into the documentation some more to figure out how to write a script transformation.  It's not that difficult, but the object model is completely...

The linked server definition I showed is from a 32-bit server.  I don't know if they have a 64-bit provider.

We use a Teradata linked server with this definition:

EXEC

master.dbo.sp_addlinkedserver

    @server = N'TERADATA'

While the list of things I don't know keeps growing daily despite my best efforts, I'm having trouble with the notion that the type of login used for a SQL...

I apologize for the error, the /3GB switch does nothing for SQL 2000 Standard, only Enterprise or Developer.  The only system I used it on happened to be SQL 2000...

There is no effect on application response.

The first major difference is that the DBA gets involved in maintaining users & passwords with SQL authentication, and applications need to have SQL...

If you can migrate to SQL 2005, snapshot isolation would probably be a great solution for whatever issue you are having.

You can't enforce ROWLOCKS at a database level because that would...

The best place to find info about this and other system stored procedures is in Books Online.  Just look up sp_help_job in the index.

The /3GB switch in boot.ini will allow SQL Server 2000 Standard to use 3GB RAM on a 4GB server.  This reduces the amount of RAM available for the operating system...

I don't believe you've posted the exact commands you've been using that are causing you problems.  This script runs successfully on one of my SQL 2000 servers, and shows the...

If the table appears in the master..sysobjects table, it was created in the master database.  This may not have been your intention, but that's what happened.