Definitely a loophole. Here we remove public and create a group in msdb that allows package creation/editing. A separate group is used for job executions on the very rare chance...

The big thing with notification from a business point of view is that we want you to come back, so not having the text (Which is the new design) works...

http://www.microsoft.com/sql/evaluation/compare/wintercorp.asp

http://www.sysinternals.com has some good utilities to see which process holds which file open.

I agree. I might drop the transform and rebuild it. Quick and easy and usually fixes issues. Print Area can be a big one as can blank lines.

I guess you could update the table manually, but I hate to do that. I'd add the new group and drop the old one.

Not sure how you do this from VB6. You can run Profiler and see all the calls made to the SQL Server. You can also load the SP in Query...

The big issue apart from dependencies that you will face with method 2 is that the items run against staging from VSS may not be the same that will run...

You still will need all other log backups prior to the current one as well as since the last full/diff backup.

A transform data task will do this in SQL 2000. SQL 7 has issues.  choose SQL Query and enter the stored procedure call on the source tab

What does that do? Sorry, not an Oracle guy.

NetIQ did a bunch of testing a couple years back and found after aroud 8-9 drives, you lose efficiency and performance in RAID 5 sets. So I wouldn't go there....

xp_sendmail has limited formatting options. I dropped ASPEmail on one of my servers and then use a DTS task (active X) to send a smaller email out to pagers/cell phones.

xp_sendmail has limited formatting options. I dropped ASPEmail on one of my servers and then use a DTS task (active X) to send a smaller email out to pagers/cell phones.

Noted and passed along to the developer.