Ravi,

If you don't go with replication or log shipping, you could still use DTS if you have a table to use as a driver.

Rather than have a "change" indicator in...

What happens when the import fails?  Any error messages?

Greg

I thought that processadmin could only kill processes.  I recommend creating a new database role in msdb, adding the user to it, and granting EXECUTE permissions to the following stored...

Mark,

Could you describe the DTS a little more?  Is the Import/Export Wizard used or has a DTS package been created?  Is the Copy SQL Server Objects task being used? 

When...

See http://www.sqldts.com/ .  If you change your mind about a book, my favorite is 'Professional SQL Server 2000 DTS' by Chaffin, Knight & Robinson.

Greg

As SQLBill says, you can't restore a single object directly into a database.  See "How to restore a database with a new name" in BOL.

Greg

If all they need to do is create tables, you could grant CREATE TABLE permission to them.  However, they wouldn't be able to drop or alter the tables they create.

Greg

I've used this article as a guide for migrating to new hardware.  Pay particular attention to the section on moving logins. 

Greg

http://support.microsoft.com/kb/314546/en-us

See "moving databases" in BOL.  This is a good article: http://support.microsoft.com/kb/314546/en-us  I'm sure I've seen stuff in the Script section of this site that will script out everything in an instance.  Try the Search...

Enable package logging and look at the log after the job runs as scheduled.  The problem is probably permissions because scheduled jobs are run under the security context of the...

I don't know of any tools that can do this in SQL 2000, but if you're planning on upgrading to SQL 2005 sometime soon, it has the ability to set...

We use MS SourceSafe for stored procedure change management and require database schema changes be made in writing so they can be documented.  We rely on backups for reversion.  We haven't...

It is not possible.  The best you can do is give the login a complex password and keep it secret.

Greg

We haven't had any problems.  We mitigate the security concerns by having everything owned by an administrative login.  Users don't own any objects and are not members of the db_owner...

I think I'd be more concerned with the performance problems caused by blocking locks than those caused by backups. 

Have you considered having the users use an application that calls stored...