Posted by jim_geissman on 10/01/54 11:42

I created a lot of procedures and functions using QueryAnalyzer from
SQL 2000. Now I have a new workstation, and installed SQL 2005.

The code on one particular server seems to be inaccessible. When I go
to edit ("modify") objects, or copy them to the clipboard, I get the
message, "Property AnsiNullsStatus is not available for <this object>.
This property may not exist for this object, or may not be retrievable
due to insufficient access rights."

Any idea how to overcome this? It seems like a minor detail that
should be fixable by setting something at a global level. BOL has
several entries for AnisNullsStatus, but I don't see anything that
looks like a solultion to my problem.

Thanks,
Jim Geissman

• Next in forum: bcp right truncation: how to ignore
• Prev in forum: [ANNOUNCE] Edit and Validate XML
• Thread view: 2000 vs 2005 -- AnsiNullsStatus

[Reply to this message]