New answers tagged

3

In and of itself, no, you are probably not adding a security risk. As long as no one but a sysadmin can alter the procedure and as long as the ONLY thing the procedure can do is start a job I don't see a problem. The risks come in with the fact that MSDB is (and is supposed to be) marked as TRUSTWORTHY. That means that by using EXECUTE AS OWNER you are ...


0

The only sure answer I can give to you is that you should be using a TEXT or BLOB datatype and not a varchar. Varchar leaves you with a chance that there wont be enough room for your data and your data can contain any type of information you require. Also (not really a problem) I would think you might be able to remove the recursive relationship in your ...


0

The issue is whether a group of operations must be treated as a single action. In other words all of the operations must be completed and committed successfully or none of the operations can be committed. If you have a scenario that requires you to read preliminary data and then perform updates based on that data then the initial read should probably be ...


6

Maybe the wording is unclear, but least privilege applies to all activities and should never be ignored. The least privilege you need to perform database maintenance is sysadmin. Lower privileged users could perform those activities too (I'm thinking of db_owners), but the least privilege needed to perform any activity on a SQL Server instance is sysadmin, ...



Top 50 recent answers are included