This article was previously published under Q279183
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 350775 (SHILOH_Bugs)
When you attempt to script an object that has a number of large, string descriptions for the value field of its extended properties, an access violation exception may occur, resulting in failure to generate the script. This problem only occurs if you have requested to script the object's extended properties when generating the script.
You may encounter this problem when you try to script the object by using SQL Server Enterprise Manager or the Query Analyzer Object Browser, or if you are using the Script method in a SQL Distributed Management Objects (DMO) application.
The length of the text for the values of the extended properties are long enough so that an internal buffer being used for building the script text is overrun.
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
NOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 1.
The English version of this fix should have the following file attributes or later:
Version File name Platform -------------------------------------- 8.00.0218 s80218i.exe x86
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.
Note that this is a client side fix, which you must install on each workstation where you intend to script an object that has several extended properties.
Clear the option to script the object's extended properties before you generate the script. If you want to see the extended properties for the object, you can use the fn_listextendedproperty system function to obtain this information, which you can then edit to generate a script that would create these same properties again.
Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.