Off-hand:

You build a cursor of orphaned users.

Within that you build a cursor of objects owned by the particular user.

You use sp_helprotect to output the permissions to a temp table.

You execute...

Unless there is a corporate policy restricting them from such tools, if they have access to the database, they can script the objects. It's one of those catch 22s. SQL...

The site uses ActiveX controls (no surprise). I think the certificate popup is because the root certificates updates Microsoft also passes down has the Root CAs for Microsoft's certificates. I...

Allow them to create stored procedures as themselves. A DBA level should be doing at least a cursory review. If it looks good, execute an sp_changeobjectowner command to make it...

Submit to Steve a bug notice (Report a problem). While I can see that some folks are able to vote, if you're experiencing this issue, likely others are as well.

There are a lot of factors that weigh into this decision, so no one is going to be able to say, "This clustering solution is best," without knowing the facts...

The only two roles that can create an object as a different owner are: db_owner, db_ddladmin. Unfortunately, they do have permissions to alter the table due to the nature of...

If you go to the SQLServerCentral.com specific page on the article, which lets you know it's an external link, there's a rating option right there on that page.

Also, within the database a sysadmin maps in as dbo, which means the sysadmin effectively ignores any security on a database object.

Then make sure you set up aliases on all physical nodes before doing the installation as per the article. Once you've gotten at least SP3 for SQL Server 2000 on...

Then I understand why Microsoft can't explain what happened. If there was no data corruption, someone (or some account) had to have dropped those stored procedures. Without more auditing in...

Are you saying both are executing at the same time? If so, and they're coming from different connections, SQL Server is going to process the one that actually came first,...

The error is important (expand the job step history to see the exact error). Keep in mind that when you execute it, it executes on your computer under your user...

Generally it's a really bad idea to do indexing against a varchar field. Out of curiousity, when selecting the clustered index, did you do so based on what's getting inserted,...

If there was no data corruption, something had to have happened which dropped those stored procedures. Does any service accounts have sysadmin access or db_owner access to the given database?...