By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,660 Members | 1,593 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,660 IT Pros & Developers. It's quick & easy.

2000 vs 2005 -- AnsiNullsStatus

P: n/a
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

Mar 16 '06 #1
Share this Question
Share on Google+
6 Replies


P: n/a
(ji**********@countrywide.com) writes:
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."


This is known issue with SQL Server Management Studio that it does not
handle user-defined functions on SQL 2000.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Mar 16 '06 #2

P: n/a
Thanks, Erland. I interpret that as: call up the code in a 2000 Query
Analyzer, and then paste it into 2005 Management Studio, which will add
the necessary stuff. Is that right? (Yes, the server is 2000.
Strange that the client would be more picky than the server.)

Jim

Mar 17 '06 #3

P: n/a
(ji**********@countrywide.com) writes:
Thanks, Erland. I interpret that as: call up the code in a 2000 Query
Analyzer, and then paste it into 2005 Management Studio, which will add
the necessary stuff. Is that right?
Not really sure what stuff that Mgmt Studio should add. You could stay in
QA if you prefer.
(Yes, the server is 2000.
Strange that the client would be more picky than the server.)


SQL 2005 has a completely new way of accessing metadata, and of course
Mgmt Studio uses that on SQL 2005, so there are different code paths for
SQL 2000 and SQL 2005.

It's of course a bug, nothing else.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Mar 17 '06 #4

P: n/a
Hello, Jim

It's an known bug, that will be fixed in SQL Server 2005 SP1. See:
http://lab.msdn.microsoft.com/produc...5-62d1fb31d0a4

Razvan

Mar 17 '06 #5

P: n/a
Thanks, Erland and Razvan.

My comment:
Thanks, Erland. I interpret that as: call up the code in a 2000 Query
Analyzer, and then paste it into 2005 Management Studio, which will add
the necessary stuff. Is that right?

Not really sure what stuff that Mgmt Studio should add. You could stay in
QA if you prefer.

....was an attempt to find a way to work on the UDF in Mgmt Studio,
because I don't have the 2000 tools on the new workstation. But for
UDFs it looks like it will be easier to stay with the 2000 client on my
laptop, as you suggest, until SP1 appears.

Jim

Mar 17 '06 #6

P: n/a
Razvan Socol (rs****@gmail.com) writes:
It's an known bug, that will be fixed in SQL Server 2005 SP1. See:
http://lab.msdn.microsoft.com/produc...5-62d1fb31d0a4


Unfortunately, they have only fixed it in part. When testing in the SP1 CTP,
I find that Modify and Script Function as Alter still fails, interesting
enough with a different error message than in RTM. The one comfort is
that Script Function as Create now works.

I've reopened the bug, so that people who sees the resolution from Microsoft
do not get false hopes.

Jim, you can run the SQL 2000 tools in parallel with the 2005 tools on
the same machine.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Mar 18 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.