September 15, 2006 at 10:34 am
Hello all,
I've install SQL2005 on my computer, but just the client tools, mainly the Management Studio. I have 2 other SQL2K servers that house our app db's and all. I've used the Studio to alter sprocs and functions but no I can't seem to access only the Table-Defined Functions I've created. When I tried to launch them for edit I recieve this error message:
"TITLE: Microsoft SQL Server Management Studio
------------------------------
Property QuotedIdentifierStatus is not available for UserDefinedFunction '[dbo].[GET_NOI]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)
-------------------------------
My permissions are proper, I can eidt all other scalar udf's, sprocs, views and tables, but just not the table-defined udf's.
Any help would be greatly appreciated.
[EDIT] I just tried to edit those table functions on a box with the old Enterprise Manager installed and it worked fine, but still not with MSSMS.[/EDIT]
Thanks,
Brian
September 15, 2006 at 3:26 pm
I have the same issue. All you can do at this time is keep the SQL 2000 client tools available for thos times you need to modify the UDF's you can't edit. I think it has to do with how SQL 2000 stores the metadata for the udf's. If you script one of the udf's and create it using the SQL 2005 tools I think you will find you still can't edit it on the SQL 2000 server with the SQL 2005 client tools.
Sorry I couldn't be more help.
September 18, 2006 at 5:37 am
I've got SQL Server Management Studio Express installed on my computer here. I tried to edit a UDF on a SQL2000 machine and experienced no problems with that. Saving on the other hand is more difficult. SSMS just opens a Query Window and shows the UDF code in which I can edit. I can only save it to a file on my file system, but not into the database itself. Weird?! Could this be a related problem?
September 18, 2006 at 5:41 am
I just found this on SQLJunkies forum:
*********************** Reply******************************
Yes, this is a known bug, and it has been resolved as fixed. It only
affects connections to SQL 2000.
See also
--
Erland Sommarskog, SQL Server MVP
*********************************************************
September 18, 2006 at 9:20 am
Thanks for your input guys/gals. I really wish they put out a hotfix for this, I hate running back and forth between computer to edit a function. It's really annoying, but I see they will consider the fix for SP2 which will be released......?
Anyway, thanks again for your help.
Brian
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply