Before SQL 2005, I've always had problems with non-sa users being able to see jobs they don't own. We couldn't even tell if someone else's job was running or not. Your DBA should be able to create a proxy account with one or more of these new SQLAgent roles enable. They are explained in detail in MSDN at this link.
The above link provides the exact permissions associated with these new roles.
Dig Deeper on Microsoft SQL Server 2005
Can Microsoft SA be a cheaper option to VDA for thin clients? If the stars align, maybe...
How to execute scheduled tasks in SQL Azure: Use SSIS packages
IEEE Standards Association (Institute of Electrical and Electronics Engineers Standards Association)
With last week's VECD licensing change, is Windows 7 now the cheapest client?
Related Q&A from Joe Toscano
Is there a query to search text in a SQL Server DTS package? SQL Server expert Joe Toscano explains which database objects can be viewed. Continue Reading
Migrate DTS packages to SQL Server Integration Services with Migration Wizard and deploy SSIS packages in SQL 2005. Learn how to access DTS Designer ... Continue Reading
Getting an error when importing data from an Excel spreadsheet to SSIS in SQL Server 2005? Try lining up data types in Excel and SSIS so they match. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.