Opinions vary about the best place to store packages. I prefer saving them as files in a specific directory and making sure the directory is included in server tape...

I guess your question is how to make the job run? I've only seen this happen when the owner is a domain account and changing the owner to sa...

Here's how I've done it:

1. Run SQL Server Upgrade Advisor on SQL 2000 to see any changes needed in DTS packages

2. In SQL 2000 Enterprise Manager, save DTS packages as...

Only the owner of the diagram i.e. the user who created it or a member of the db_owner or sysadmin roles can open a diagram.

We have developers use...

Can you describe how you enabled logging and specified the events? Did you follow the steps described here?: http://msdn.microsoft.com/en-us/library/ms141212(SQL.90).aspx

Please clarify whether this is a DTS package or an SSIS package. In either case, logging must be enabled in the package before any logging takes place and you...

There's a fixed database role in msdb whose members can list and view the properties of jobs, but doesn't allow editing the properties. It's called SQLAgentReaderRole. Ask you...

I'm pretty sure you'd have to search for the text (insert, update, etc) in the source code of the stored procedures which is stored in syscomments.

This article describes...

Does the user query the table directly via Query Analyzer or does it use a stored procedure? Try running this to see what permissions are granted for the table:...

I actually don't think it's all that inefficient to calculate the date in each step, but you could calculate it in the first step and write it to a table...

I don't know if this is more elegant, but you could create a separate monthly schedule for each day from the 21st thru the 31st. That would mean you'd...

I like to use RESTRICTED_USER rather than SINGLE_USER to make sure I'm the one who can connect to the database.

Twice a day won't do much about keeping the logs manageable, but it really depends on how much update activity there is. I'd start with hourly backups and adjust...

RP_DBA (5/21/2009)

---

If it's a one-off, I'd go with the import/export wizard. If this is something you'll need to repeat down the road, you might consider writing code (i.e. SP) to...

You can't prevent SQL Server from writing to the transaction log. It's an integral part of the database engine. Since the package runs so often, you should consider...