Okay, copy the script in full from this site and run it in the appropriate database (don't do anything past that point). Let me know if it at least creates...

Do you have the "@v_Output_Mode" parameter in the script?

It might, or at the least be easier to trouble shoot. The latest version is the one currently posted on SSC.com:

http://www.sqlservercentral.com/scripts/Administration/70243/

There were some changes to the script recently. Do you have the latest one?

Excellent article. Best read of the week. 🙂

Good idea and thanks for posting this. I may end up adding a "use or search" for wildcards switch in a later version. This would make it more flexible.

When I originally designed the procedure it actually functioned the way you wanted it to. After a peer review with some colleagues, they all argued for the opposite (never can...

My pleasure. Hope you find it handy.

Superb article. Well worth the read.

If you need to include the schema, then something like this should do the trick:

FROM

'+@v_Database_Name+N'.[sys].[schemas] S

INNER JOIN '+@v_Database_Name+N'.[sys].[objects] O ON O.[schema_id] = S.[schema_id]

AND O.[type] IN ('+(CASE

WHEN @v_Object_Types IS NOT NULL...

You can modify the code temporarily by adding at line 232:

AND O.name = 'MY_TABLE_NAME'

So something like this:

FROM

'+@v_Database_Name+N'.[sys].[schemas] S

...

Thank you. I hope you find it useful. 🙂

No problem. I seem to remember something about certain "date / time" columns in some of the system tables having ridiculous values (sometimes) for some reason which could be the...

Are you able to isolate the SPID throwing the error? If yes, are you able to identify the column in question?

The latest changes are now online!